Live data from Hacker News

Java 16

jdk.java.net

101–110 of 327 posts

Re: Java 16

#101

Java 16 for what? Does anybody really use > 8 in production?

Who still uses Java 8 in production? That is a serious risk. I thought everyone moved to 11 already.

I use Java 15 in production in 3 projects.

Re: Java 16

#102
post #94

Java devs are like: Why bother to develop anything new if we can just copycat every single feature from C# without even changing their spec a bit... C# records released last year: record Book(string Title, int Id); New java records: record Book(String title, int id)

[deleted]

Re: Java 16

#103

Lots of shiny new toys to play with :) I like playing with new features and pushing to silly limits. Here's some fun things you can do now: Compiletime checked state machines with Sealed Classes [preview feature] https://benjiweber.co.uk/blog/2020/10/03/sealed-java-state-m... Autobuilders, Mixins, Conversions & more with Records https://benjiweber.co.uk/blog/2020/09/19/fun-with-java-recor... Pattern Matching fun http…

If you enjoy pattern matching in Java, I would recommend checking out the latest & greatest that C# has to offer as a comparison:

https://docs.microsoft.com/en-us/dotnet/csharp/pattern-match...

Being able to combine pattern matching with switch expressions has allowed us to construct extraordinarily concise state machines for our UIs.

Re: Java 16

#104
post #75

Earlier quoted context omitted.

> Why bother investing in the languages with a much smaller market share when the big boys adopt good bits and pieces from them constantly? This won't always apply, but sometimes (many times?) there's a software endeavor that permanently feels on the margins of a programming language's capabilities, whatever that means. You may forego market share in order to be 5 or 10 years ahead of current practice. In other words…

Another thing to note that cutting edge languages do not always deliver great features , they also deliver with great frequency half baked features to be discarded or deprecated in few years. Also since most effort spent on language , tooling remain primitive and slow for long time. So I do not see them a sure win for projects I work on.

FWIW, I feel that way about Scala, but not F#.

The only big F# feature I know of that's fallen out of favor is type providers, and, IMO, that's not because the feature was half-baked so much as because it was one of the many casualties of .NET's transition to being a truly cross-platform toolkit.

Re: Java 16

#105
post #47

Earlier quoted context omitted.

There is an nginx in front of it. What was wrong with Apache?

Apache feels like a forgotten gem in the ops world. Everyone moved onto Nginx and at some point will run into some use-case that needs a feature that's only in Nginx+. And since Nginx+ is so expensive people end up just patching the OSS Nginx with the modules they need. But that whole time Apache was there with every conceivable battery and feature already included.

[deleted]

Re: Java 16

#106

Still on Java 8 at work :-/

Every thread about new Java version has the same comment all the time. Why share it? What kind of response do you seek?

I think it's interesting to discuss how many are stuck on java8. It was a long time many of us were stuck on java6 or 7, and finally got up to java8. But then when 9, 10 and 11 came no one made an effort to upgrade. Why? And now we're at 15 and people are starting to feel the heat.

We only migrated our main service from 8 to 15 a month ago (AWS deprecation), but still have lots of 8 code laying around (luckily some of the container-features were backported)

Re: Java 16

#107
post #3

Why they decided to change the keyword rules to use "non-sealed" is beyond me. Surely, there might be other choices? Closed/unclosed? Unsealed?

It's the same story in C++, co_await, co_yield. The sole purpose is not to break other people's code.

co_await is so bad that co_X has become a running joke in the C++ community.

Re: Java 16

#108
post #12

Very cool to see that Scala continues to have a huge impact on Java’s roadmap. Records and Sealed Classes are borrowed from Scala. Could be not the best news for new Scala adoption, but good news for developers having better abstractions in Java Edit: Kotlin, and other languages should also mentioned since they also include similar features. I still think Scala has had the most influence over the years.

I think Kotlin is more at risk than Scala on the server at least. Scala still has a lot of advanced features that sets itself apart. Kotlin is a better Java but Java is catching up fast.

Re: Java 16

#109
post #94

Java devs are like: Why bother to develop anything new if we can just copycat every single feature from C# without even changing their spec a bit... C# records released last year: record Book(string Title, int Id); New java records: record Book(String title, int id)

C# started adding records when Java was already working on them.

So if you insist on someone borrowing, it is this time the other way around.

Re: Java 16

#110
As a student most of the way through a Java course, I'm wondering what Java is still used for. Java applets are dead, Android is moving on to Kotlin (apparently Google got in legal trouble with Oracle even though Java is "open source?"), and I can't think of any desktop applications that use Java anymore. Java is supposed to be able to "run anywhere," yet C++ is more portable because it doesn't require the JVM to run.

Yet clearly I'm mistaken, since Java is still one of the most popular languages.

Edit: also please help me understand - do I have to pay for a license even though Java is open source? Is this normal for other languages too?

Post reply on HN