41–50 of 526 posts
But it is the right thing to do. Oracle is not trustworthy.
> the worst case possible, as it not only voids the “WORA” (Write Once Run Anywhere) principle, it simply won’t happen in reality: After 18 months virtually no application vendor really wants to spend the time and money to update all customers with recompiled versions just for the sake of a renamed platform with a dubios future. WORA was never perfect, I would be surprised if there was even a single JRE release that…
Earlier quoted context omitted.
Before the language becomes a performance bottleneck there is so much stuff to consider that it quickly becomes clear how the choice of language doesn't really make a difference, except in special cases such as embedded systems.
A language that requires C for anything regarding performance is only useful for scripting and learning to program.
Earlier quoted context omitted.
Good luck with the performance over there.
The hot parts we can implement in C. There's not much overhead in crossing over to native code.
With C being an incredibly difficult language to get right.
So difficult that languages like Go and Rust were invented.
Earlier quoted context omitted.
That is not Python.
It's real-world Python. Why do you think stuff like SciPy are so popular?
Two languages to learn. Two languages to support. Two development environments. Two build tools. Two CI/CD pipelines. Two testing infrastructure. Two sets of code and security reviews.
Double the complexity and for what exactly ?
The Java ecosystem has been slowly dying for years, it's already the new Cobol at this stage. I have the impression that a lot of the mindshare has switched to the Node and Javascript ecosystem, especially the frontend devs, via the Typescript / Angular path, which is a natural path to Java developers due to the comfort given by familiar concepts like static types, classes, etc. When I used to do Java, I always found…
Working in the JVM world I'm always surprised to hear that its dying, the JVM and Java moves faster forward than ever, Graal is about to go 1.0, a bunch of very interesting (very) low latency GCs are in the pipe (for example ZGC and Shenandoah) and lots of other interesting projects like Valhalla promise to keep the JVM relevant for the next 20 years. Oracle have made some moves to monetize on parts of its investment…
At any given time most developers will neither have much real choice when it comes to technology nor have a longer term perspective. Hence most developers will stick to what they know and what organizational inertia seems the path of least resistance.
The comparison to COBOL is good for several reasons.
Earlier quoted context omitted.
A language that requires C for anything regarding performance is only useful for scripting and learning to program.
I mean, what do you think the Java VM is written in?
Because as a developer I am exclusively writing in a language that sits on top of the JVM. I don't ever need to write in the language that the JVM itself written in.
The Java ecosystem has been slowly dying for years, it's already the new Cobol at this stage. I have the impression that a lot of the mindshare has switched to the Node and Javascript ecosystem, especially the frontend devs, via the Typescript / Angular path, which is a natural path to Java developers due to the comfort given by familiar concepts like static types, classes, etc. When I used to do Java, I always found…
Earlier quoted context omitted.
Before the language becomes a performance bottleneck there is so much stuff to consider that it quickly becomes clear how the choice of language doesn't really make a difference, except in special cases such as embedded systems.
A language that requires C for anything regarding performance is only useful for scripting and learning to program.
The Java ecosystem has been slowly dying for years, it's already the new Cobol at this stage. I have the impression that a lot of the mindshare has switched to the Node and Javascript ecosystem, especially the frontend devs, via the Typescript / Angular path, which is a natural path to Java developers due to the comfort given by familiar concepts like static types, classes, etc. When I used to do Java, I always found…
I would not go as far to say it's dying but it's heavily slowing down for sure. First because of the big move out of the "entreprise" software and secondly because of Oracle legal team. It's definitely due to the licensing that Android is switching to Kotlin for example.