Oracle contributes patches to OpenJDK, for instance lambda support.
Do you want less of that? Are the commits made by Oracle employees especially bad?
It's not like you need to use the Oracle JDK. There are many different distros, just like Linux.
114 karma · joined September 6, 2017
Oracle contributes patches to OpenJDK, for instance lambda support.
Do you want less of that? Are the commits made by Oracle employees especially bad?
It's not like you need to use the Oracle JDK. There are many different distros, just like Linux.
Java is still free, so it can't be that.
This doesn't happen often.
It's definitely not a research project. There are many large companies who contribute to OpenJDK, for example Oracle, SAP, Red Hat, SAP, Google and Amazon
https://blogs.oracle.com/java-platform-group/building-jdk-11...
Should it have been there from the beginning. Yes, but it would have delayed the release of JDK 1.0.
People often complain about type erasure, but I have seen very few examples of everyday programming where it would have helped. I think type erasure was a reasonable compromise.
The only real use case I can see is value types.
You want List<int> to be backed by array of ints, not Integer objects. But there are already plans to add this to JVM, once value types are added.
I don't like distributed version control systems with hundreds of repositories spread out. It makes management more complicated. I understand this is a minority view, but that is my experience. It was easier to work in a single Perforce repository than hundreds of Git or Mercurial repos.
Fibers, pattern matching, continuations, value types, low latency garbage collector …
The greatest trick the Devil ever pulled was convincing the world he didn't exist.
Also, JDK 11 (Hotspot) comes with a new concurrent non-generational garbage collector (ZGC) [3] that has an average pause time of 1 ms [4]. It is still an experimental feature, but that will most likely change over time.
[1] http://cr.openjdk.java.net/~rpressler/loom/Loom-Proposal.htm...
[2] http://openjdk.java.net/projects/loom/
Setting up the wallet doesn't need to be more complicated than setting up a card with Apple Pay. You don't need to understand the underlying technology to use it in millions of stores.
Today's system is like setting up Apple Pay every time you need to buy something in a store you have not visited before. It's a horrible user experience.
The JDK libraries has also grown. You could probably spend a week just learning about java.util.concurrent.* and how to write efficient multithreaded code.
With microtransactions you only pay for what you want to consume and you don't need 10+ different subscriptions. That is the benefit.
If you only want to spend 2 dollar a month, that's fine.
The user doesn't need to know what a cryptocurrency is, the dialog will be displayed in dollar, or whatever currency you happen to use in your country.
Today's system is more complicated. You have to create an account, confirm e-mail, remember your password, enter credit card number, address, expiration date etc.
When you visit a web page, you can pay for the content by clicking Yes in a dialog box. When you don't have money in you wallet, you can fill it up using your credit card, or some bank solution. The price is shown in your currency of choice, but all the transactions happens on the blockchain.
People who make web pages can paste in some javascript to charge for content. No third party organization needs to get involved and the seller can't get charge backs. The transaction fee will be low so that you can charge pennies for a news article. This will work without you giving away you credit card number, name, address, e-mail etc. to the seller.
Not sure this is a better strategy - it accumulates technical debt.
I think you should try to update as much as possible and stay ahead of the curve. That way you can reap the benefits of performance improvements, bug fixes and richer APIs. Sure, it makes sense to not use the bleeding edge, but being on the oldest possible version doesn't seem to be a good strategy either.
I thought each register, i.e. BC or DE, had its own stack. I couldn't understand why some programs crashed. Very frustrating when you had to reload everything from tape again, and again, and again...
http://cr.openjdk.java.net/~rpressler/loom/Loom-Proposal.htm...
Data classes may come to Java.
http://cr.openjdk.java.net/~briangoetz/amber/datum.html
http://mail.openjdk.java.net/pipermail/amber-spec-experts/20...
Fibers, continuations, string literals, pattern matching and value types are in the works.
http://cr.openjdk.java.net/~rpressler/loom/Loom-Proposal.htm...
http://openjdk.java.net/jeps/326
I wonder how the numbers would have looked with the new low latency GC for Hotspot (ZGC). https://wiki.openjdk.java.net/display/zgc/Main
Early results from SPECjbb2015 are impressive. https://youtu.be/tShc0dyFtgw?t=5m1s
Collections.emptyList() Collections.singletonList() Collections.unmodifiableList() List.of()
As niftich points out, use the marker interface java.util.RandomAccess, if you want to know if the list allows constant time access.
Results from Altavista, Bing and DuckDuckGo are so much worse.
Note, it's not that Google has personal information on me. I'm not logged in, my cache is cleared, I use a VPN and google.com/ncr when it was available. Not sure how they do it. Perhaps their tracker sees how long people have visited a page and then they give those pages higher priority.
Perhaps other search engines can do a better job, but they had over a decade to improve their results and they are still far off.
"Most Java web servers work by starting a new thread of execution for each request that comes in "
Nobody who has a performance critical application starts a new thread for every request.
That would be beyond stupid.
1) Transparency. I can see what everybody else is doing and if somebody has an interesting project I can find it quickly. You can also learn a lot from looking at other peoples changes.
2) Faster. To check out the source code for the project I now work on takes an hour in the distributed system, while it only took 5 minutes in the centralized system.
3) Always backed up. All code that is checked into the central repository is backed up. It has happened twice that employees have left and code was lost because they only checked it in locally.
Many have only used CVS or SVN, which are horrible. I rather use Git or Mercurial, but Perforce is really good.
I want to build amazing software, and for that I need a larger company who can market my inventions and talk about it on conferences and road shows.
I will earn less, but I will be happy.
- more efficient representation
- thread safety
- security (defensive copy)
- validation
- logging
- debugging
- backward compatibility
If GC pause times do not increase with the heap- or live-set size, it could handle such large heaps.