Java in 2024 - Constant evolution, delivered.

Oracle DevLive New York - Java Day™ Keynote
As the world of modern application development rapidly evolves, Java continues to adapt to keep pace. This affords enterprises the ability to accelerate mission-critical application development reliant on Java and provide developers a programming language and platform that efficiently and effectively address app development from on-premises to the cloud. In this keynote, Java luminaries from Oracle explore modern Java features that enable next-gen applications, as well as cover how Oracle’s ongoing Java technology leadership and ecosystem stewardship are creating a contemporary language and platform that help advance developer productivity and Java community participation.
Presented by Georges Saab - Senior Vice President of Development (Java Platform Group) and Chad Arimura - Vice President of Java DevRel (Java Platform Group).
Resources
➲ openjdk.org
➲ dev.java
➲ inside.java
Tags #java #JDK #oracle

[@lmj5994]

Can we stop making every Java conference about the switch to 6 monthly releases ? I love 6-monthly releases, don't want to go back, ever, BUT does every conference need to make a big thing of it over and over ?

[@cosmowanda6460]

Right, they've brought it up on pretty much every talk like it's a new thing. It's annoying to listen to them spend time talking about that when they could talk about something else with their "limited time"

[@ramadansevgin6391]

Тhis language is unique (Java Forever) 🥰🥰

[@curio78]

They need to deliver the project valhala.. which is universal generics and value types without delay. .That is the only thing that is currently such a pain in developing performance libraries. Because that will bring the most drastic changes in how API are built in every library. Better early as it takes time for everything to move.

[@lepingouindefeu]

Yes, we've been waiting for so long.

[@loic.bertrand]

Yes, but I'd prefer that they take their time to do it right: without introducing backward incompatibilities, without adding ceremony to Java code (exclamation marks everywhere in the code to mark non nullable types) and by enabling existing classes to be migrated to value classes etc

[@curio78]

@@loic.bertrand Non-nullable is not that crucial, that can wait. Honestly, I do not see much value in it, there was some talk about it being needed to flatten out the heap. But I just do not get why null value types be not flattened?? maybe I am missed something. I am specifically talking about 3 things Value Types, Value types handled in stack and most importantly universal generics. If they can deliver on the first two, there won't be so much complaining about universal generics. Just having value types without JVM changes to handle it in stacks, also brings nothing to performance. To be honest these three needs to be done together. as they alter the way you write code and libraries. Delivering these piece-meal is not ideal. And finally, I said they need to hurry is because JEP 401 (value types) was expected to be in 21.. then it was 22 now it's not even going to be there in 23. Given the plan was to bring the changes one by one value types first/ stack handling next and finally universal generics. Do you see the problem?? it's almost like you can forget about them until JDK 30!! somewhere in 2028. I would prefer them to bite the bullet and just deliver value types and universal generics together in preview in jdk 25 then focus on performance of stack in the subsequent release. At least you will have the lead time to change the libraries.

[@curio78]

@@loic.bertrand And the only reason i am complaining so much is because I just had to tear apart ta4j library and go column wise data structure style of primitive just make it useful for back testing. I would have preferred not to do that given now everything is of one type as no generics can be used. But there is no other way right now, as the difference in performance is an order of magnitude different. Which is an absolute necessity for being able to automating rule discovery. The API is well written right now but not of much use given the performance it has.

[@prdoyle]

Valhalla will be nice for sure. Different folks value different things... I'm really looking forward to structured concurrency and the classfile API.

[@TochukwuVictor-qe4xd]

Nice one ❤

[@onebeartoe]

I like this speed-presenter format.

[@kirillalexander-rj2im]

Oops, I misread as constant evaluation...

[@aecbnas2112]

When will valhalla come to us?2025 or 2030!

[@algo-prog]

The first like ....

[@AkbarKhan-gd2bw]

I have an Idea for you why don't you guys upload java tutorial from beginning to advance , you guys develop it so you guys can make very good tutorial also

[@monisahmedrizvi1697]

i think they do have learning platform , not sure about the name . java is owned by oracle and you know what happens when greedy company gets its hands on things they charge you insane amount , better learn from java mooc course you can find it , or through udemy , lot of good video of youtube as well

[@D_bugit]

😂😂😂... Smart guy

[@chrigenevodounon6063]

Bro wants homemade tutorials 😂

[@urosjarc3450]

It's really nice that Java is finally starting to waking up.

[@brayanmnz]

When was it sleeping?

[@pompiuses]

Still missing null safety like Kotlin or C#. This is probably THE most requested feature by junior programmers. Why this isn’t a higher priority at Oracle is beyond me. At my organisation this is the biggest reason why younger programmers shy away from Java.

[@Rope257]

I highly doubt it's null-safety that turns away younger programmers. Most courses nowadays use Python and Python has the same issue. People just like to shit on Java for no particular reason other than it's "old". It's an image issue with no real foundation.

[@lepingouindefeu]

I'm sure they have a reason for not implementing null safety yet. Probably waiting for project Valhalla, since that seems to have a major impact on the feature.

[@imakhlaqXD]

​@@Rope257 its not image issue. its syntax is ugly and its hella bloated.

[@cstates94]

If Junior Devs are actually complaining about that, I wouldn't trust them with Kotlin or C# features either. If you can disable them, I'm not trusting them. We have Optionals and @NotNull. If someone returns a null Optional, that's a skill issue.

[@Rope257]

@@imakhlaqXD Bloated how? What would be an example of a syntax that's not bloated and ugly? Typescript? Typescript basically has the same syntax just with the typing after an identifier instead of in front of it. Yet typescript is popular. Maybe Python? Because it uses indenting instead of curly braces for implicit instead of explicit code-blocks? Is C# better? Because that's basically the same syntax too.

[@chrigenevodounon6063]

How are you going to do Oracle? Promise to catch up.

[@nesdi6653]

data

[@monisahmedrizvi1697]

its sad that oracle owns it

[@Drekrosh]

The Oracle is vainly trying to save its language from extinction. Unfortunately for them, it’s all over, and they’re too late. In typical Oracle fashion, they will show a graph predicting that by 2050 there will be LTS and JDK version 100500, which will just catch up to the features and capabilities of languages as of 2024. Worse still, many are still stuck on Java 8 and cannot afford to switch to another version. Instead of making it easier for such people to transition, they invent some nonsense, boasting about new features that no one will use. Modern projects are starting with Golang and Rust, while Java remains only for maintenance (they are gradually rewriting it). From all this, it follows that they should just focus on developing the JVM and that’s it. They should declare that they can no longer develop the language and concede to stronger and more reliable languages like Rust, Go, or Kotlin. In short, the presentation was very funny. Oracle with its dinosaur is clownish.

[@D_bugit]

Are you done?

[@Drekrosh]

@@D_bugit Sure

[@murilovieira2785]

Kotlin...

[@lepingouindefeu]

I mean, you're not wrong, but still...

[@Drekrosh]

@@Jay151 Dude, your enterprise is java 8, no one to take Java for new features.