Live data from Hacker News

Oracle finally targets Java non-payers six years after plucking Sun

theregister.co.uk

41–50 of 91 posts

Re: Oracle finally targets Java non-payers six years after plucking Sun

#41
post #10

How real is this and what impact, if any, would this have on server apps that run on a JVM? There's tons of them, many of which bundle a copy of the JVM in the app itself. The latter is the suggested deployment model in containers (i.e. bundle all your dependencies). Also, would using OpenJDK remove any " Get your ass sued by Oracle " risk or just defer it to a later date?

Absolutely. By all means bundle the JVM because it is a dependency, but do not bundle Oracle's JVM/jre in your container images.

Re: Oracle finally targets Java non-payers six years after plucking Sun

#42
post #13

There is so much negativity around Java that I wonder why anyone starting on their journey to becoming a programmer would want to learn it or work with it.

Outside of HN, it's not very different than any other mainstream language, and I'm saying this as someone who doesn't work with Java at all.

Re: Oracle finally targets Java non-payers six years after plucking Sun

#43
post #24
post #4

Are there still any reasons why one should choose Java instead of .Net for new developments?

There are many, many more good libraries for Java in Maven Central than for .NET in Nuget. OS independence, if not quite platform independence, has informed much of those libraries' development. Maven, love it or hate it, can do a staggering number of things, some of them very useful. JAX-RS servers and clients are more robust IME on Java. (Just try to find a capable path+querystring builder for .NET.) JDBC is still…

Maven, where your build script is actually declarative XML that might or might not run. Maven, which spends a minute contacting random servers all over the world only to tell you there is a closing tag missing.

I still have a repository where Surefire (hah) refuses to run any tests. Impossible to debug. No, that pile won't be missed.

Re: Oracle finally targets Java non-payers six years after plucking Sun

#44
post #13

There is so much negativity around Java that I wonder why anyone starting on their journey to becoming a programmer would want to learn it or work with it.

"There are only two kinds of languages: the ones people complain about and the ones nobody uses"

-- Bjarne Stroustrup [1], Creator of C++

[1] http://www.stroustrup.com/bs_faq.html#really-say-that

Re: Oracle finally targets Java non-payers six years after plucking Sun

#45
post #13

There is so much negativity around Java that I wonder why anyone starting on their journey to becoming a programmer would want to learn it or work with it.

It's the language of choice in most college programs. Though I won't be surprised if Javascript supplants it. Node.js feels like the new JVM. And it even has Clojure running on it.

Re: Oracle finally targets Java non-payers six years after plucking Sun

#46
post #35

Great news for Golang. Time to switch if you have not.

Go doesn't share any kind of similarity in purpose, methodology or audience with Java. Or maybe you were being sarcastic?

It fits the generic GC performant network server designed for large teams in mind. A large segment in Java land.

Re: Oracle finally targets Java non-payers six years after plucking Sun

#48
post #4

Are there still any reasons why one should choose Java instead of .Net for new developments?

The JVM: it is not only Java than runs on it, but Scala, Clojure, Ceylon, etc. Although many of these languages support other compilation targets (JavaScript, for example), the JVM is always their main and most powerful platform.

Re: Oracle finally targets Java non-payers six years after plucking Sun

#49
post #24

Earlier quoted context omitted.

There are many, many more good libraries for Java in Maven Central than for .NET in Nuget. OS independence, if not quite platform independence, has informed much of those libraries' development. Maven, love it or hate it, can do a staggering number of things, some of them very useful. JAX-RS servers and clients are more robust IME on Java. (Just try to find a capable path+querystring builder for .NET.) JDBC is still…

Maven, where your build script is actually declarative XML that might or might not run. Maven, which spends a minute contacting random servers all over the world only to tell you there is a closing tag missing. I still have a repository where Surefire (hah) refuses to run any tests. Impossible to debug. No, that pile won't be missed.

I will rather take Maven a full day over a few seconds with Gradle.
Post reply on HN