Live data from Hacker News

Negotiations Failed: How Oracle Killed Java EE

headcrashing.wordpress.com

81–90 of 526 posts

Re: Negotiations Failed: How Oracle Killed Java EE

#81

Earlier quoted context omitted.

OpenJDK is an open distribution and preinstalled on all major operating systems and is now the standard JVM for most developers. We even have open distributions of it e.g. Amazon Coretto. GraalVM isn't even at version 1.0 so nothing at all to worry about.

Since when OpenJDK is preinstalled on Windows?

... and iOS? And I’ve only done upgrades, but I don’t believe any JVM is preinstalled on MacOS.

Re: Negotiations Failed: How Oracle Killed Java EE

#82
post #32
post #10

« Oracle already started a blocking politics at the Eclipse Foundation’s board, where Oracle has a seat, and where unanimous decisions are needed. Oracle now has the power, and apparently will use that power, to block the foundation’s future. It demonstrated that power already in a board meeting, where they had the sole vote against an otherwise unaimous move. » I hope other organisations with a director from Oracle…

For me it's more a lesson about how unanimous votes, or unanimous - N can become problematic. In the EU the same is happening. Poland and Hungary have found a loophole allowing them to ignore EU rules and sanctions while still profiting from subsidies and market access. All sanctions against a member state require unanimous-1 (all states except the sanctioned member) votes and Poland is vetoing all sanctions against…

It’s an old Polish tradition:

https://en.wikipedia.org/wiki/Liberum_veto

Re: Negotiations Failed: How Oracle Killed Java EE

#83
post #74
post #70

Earlier quoted context omitted.

No, in practice is works something like this: 1) write everything in python 2) yeah, the performance here is good enough so ship it 3) there is no 3 There are very few situations where performance is going to be an issue for you where there is not an existing C module solution that will solve the problem for you. The tired old 'python is slow' trope is getting more and more irrelevant every day. There are other aspec…

Reddit disagrees. And they weren't using 3, which is even slower.

By using Python they were able to ship, which is why you have heard of Reddit and they were able to grow enough to have a concurrency problem (something Python still sucks at); the number of sites of any significance that started by using Java for page delivery is probably somewhere around 0.

Re: Negotiations Failed: How Oracle Killed Java EE

#84

Earlier quoted context omitted.

Kotlin is owned by JetBrains not Google. And there is Kotlin-Native but the likelihood of JetBrains reimplementing the entire JVM SDK is pretty slim. Not to mention all of the common third party libraries e.g. Guava, HTTPClient.

> Kotlin is owned by JetBrains not Google. Yes but there's a lot of efforts from Google to support the language as well since now it's the new Android language.

Android supports Java, Kotlin and C++.

Kotlin is just one option more, and the tooling is still not mature as Java.

Specially in compile speed, incremental compilation, debugging, speed in type completion, FFI.

Re: Negotiations Failed: How Oracle Killed Java EE

#85
post #41

Oracle makes Java a risk factor in all projects. I stopped approving new Java projects in my team 2 years ago after we switched to Go. This wasn’t a decision we took lightly and it took almost a decade for me to be comfortable with leaving Java behind. But it is the right thing to do. Oracle is not trustworthy.

Strange attitude to take when you can just target OpenJDK and then it is completely irrelevant what Oracle does or does not do. The fact is that every single one of the largest companies has some Java or Scala code within their core platform. And none of them have ever raised Oracle as a risk.

The most valuable corporation in the world as of this date uses zero Java for anything “core”.

Anecdotally, nearly every CIO/CTO I’ve encountered in the last few sees Oracle as a huge risk. Most particularly with regards to databases, which are even sticker than applications which have shorter life cycles.

Re: Negotiations Failed: How Oracle Killed Java EE

#86
post #83
post #74

Earlier quoted context omitted.

Reddit disagrees. And they weren't using 3, which is even slower.

By using Python they were able to ship, which is why you have heard of Reddit and they were able to grow enough to have a concurrency problem (something Python still sucks at); the number of sites of any significance that started by using Java for page delivery is probably somewhere around 0.

They would be able to ship in any language, that is what software engineering is all about.

Re: Negotiations Failed: How Oracle Killed Java EE

#87
post #14

Earlier quoted context omitted.

The hot parts we can implement in C. There's not much overhead in crossing over to native code.

Lovely theory, but in practice it works more like this: 1) write everything in python because its easy and quick to do so. 2) its slow as. 3) abandon software and write it in something else, or, live on with slow ass software and blame python for being slow and rubbish forever more. re-writing python in c is a hideously painful process, and its proven to be very unsuccessful practically. Writing new code in c/c++/wha…

Nope: Cython + Numba always sufficed so far

Re: Negotiations Failed: How Oracle Killed Java EE

#88
post #65
post #14

Earlier quoted context omitted.

The hot parts we can implement in C. There's not much overhead in crossing over to native code.

You'll always need more performance so you'll end up rewriting big parts of the codebase in C because you can't afford the servers and/or can't scale anymore. You'll be kicking the can down the road again and again. Also C is hard. At that point you will realise using Python was a stupid idea when you had other options like Go. It has happened to many people.

I don't think I've ever seen a commercial Python codebase that actually did rewrite things in C for speed.

Much more likely is using a library like NumPy where someone else has done that C performance work for you.

Plus in 2019, it's much cheaper to design for horizontal scale and spin up a few more instances.

Re: Negotiations Failed: How Oracle Killed Java EE

#89
post #78

> And the idea that corporate developers or even frankly any developers are switching to LLVM and WebAssembly en masse is pretty ridiculous. There is only 1 popular language released since 2009 that targets JVM: Kotlin. All other target JS, their own bytecode or LLVM: Go, Rust, Dart, Elixer, Julia, Typescript, Swift. This is a significant difference from 2003-2009 languages which all targeted JVM unless they were Mic…

And all of them have a lot of work to catch up with 25 years of market experience.

Re: Negotiations Failed: How Oracle Killed Java EE

#90
post #69
post #60

Earlier quoted context omitted.

Kotlin is a JVM language, sold as a better Java, and the JVM is really the thing that is the echo system gathers around, not necessarily the language Java. Other interesting languages you have on the JVM is Scala (multi-paradigm), Clojure (Lisp), EtaLang (Haskell) - https://eta-lang.org - https://www.scala-lang.org - https://kotlinlang.org - https://clojure.org

Notice how I separately addressed JVM and Java. Java is already losing market share to JVM competitor languages. JVM is in a stronger position than Java, but imagine a world were 15-10 years ago native compilation for JVM bytecode became available instead of 1 year ago. LLVM wouldn't have stood a chance. Kotlin and Scala (I'm not too familiar with Clojure and others) are hedging their bets and making JS/Webassembly a…

JVM native compilation exists since 2000 for anyone willing to pay for it.
Post reply on HN