5 ms·
Java 23 / JDK 23: General Availability
- carimura 2y agonftc download: https://www.oracle.com/java/technologies/downloads/ https://www.oracle.com/java/technologies/downloads/ live stream https://www.youtube.com/watch?v=QG9xKpgwOI4 https://www.youtube.com/watch?v=QG9xKpgwOI4
- gigatexal 2y agoFrom the link/mailing list announcement: “JDK 23, the reference implementation of Java 23, is now Generally Available. We shipped build 37 as the second Release Candidate of JDK 23 on 21 August, and no P1 bugs have been reported since then. Build 37 is therefore now the GA build, ready for production use. GPL-licensed OpenJDK builds from Oracle are available here: https://jdk.java.net/23 Builds from other vendors will no doubt be available soon. This release includes twelve JEPs [1], including the switch of ZGC’s default mode to the generational mode (474): 455: Primitive Types in Patterns, instanceof, and switch (Preview) 466: Class-File API (Second Preview) 467: Markdown Documentation Comments 469: Vector API (Eighth Incubator) 473: Stream Gatherers (Second Preview) 471: Deprecate the Memory-Access Methods in sun.misc.Unsafe for Removal 474: ZGC: Generational Mode by Default 476: Module Import Declarations (Preview) 477: Implicitly Declared Classes and Instance Main Methods (Third Preview) 480: Structured Concurrency (Third Preview) 481: Scoped Values (Third Preview) 482: Flexible Constructor Bodies (Second Preview) This release also includes, as usual, hundreds of smaller enhancements and thousands of bug fixes. Thank you to everyone who contributed this release, whether by designing and implementing features or enhancements, by fixing bugs, or by downloading and testing the early-access builds! - Mark [1] https://openjdk.org/projects/jdk/2/“ https://openjdk.org/projects/jdk/2/“
- deleted 2y ago[deleted]
- Alifatisk 2y agoWhich variant of JDk is common for personal use? Is it still Temurin?
- vips7L 2y agoAny of them except for the Oracle Commercial build.
- macinjosh 2y agoI need someone to sell me on Java. I might need to learn it soon for a project but it never before occurred to me that it is something I should use. I came up in coding in the early 00's. To me Java was that slow, buggy, sometimes dangerous browser plug-in that I think most people loathed? On Mac OS X at least Java desktop apps were always slow, ugly, and broke the platform UI conventions. Then Java was that language Google used for Android and then ended up in a long, expensive lawsuit over it with Java's owner Oracle. It is cross-platform as a big selling point but then people use it to write monolithic server applications where cross-platform capability isn't useful. It seems to be kinda, sorta open source but don't fuck up with the licenses or Larry's lawyers will come for you. I'd rather just use a fully open language where the community can guide its progress. I am sincerely not trying to start a flame war or be condenscending. I would like to expand my thinking and understand what I am missing out on.
- the8472 2y agoJava is mostly used for server applications and occasionally for desktop apps (e.g. IntelliJ) these days. Applets aren't relevant anymore since all browsers removed them. Java is memory-safe, multi-threaded and JIT-compiled. Faster than python, safer than Go or C. It has good tooling (debuggers, profilers, IDEs). It was one of the first languages to bring safe shared-memory multi-threading to the table, its memory-model came before C++'s. Its FFI story has been lacking for a long time, but this has been improving with java.lang.native. Over the years it has adopted a lot of nice features that other languages have mainstreamed. So 2000s Java is not 2020s Java. The JVM can also run a bunch of other languages. There are many 3rd-party, FOSS builds of the JDK, so you don't need to use oracle's builds. GCs have improved a lot. Lower latency, more parallelism, more throughput. Though they still need a good amount of RAM as breathing room. Startup times and memory consumption can still be an issue. They're working on value types that should help with memory efficiency too. And as with any language: even if the base language is fine, a project can still make it hell. Extremely convoluted "Enterprise Java" projects that layer interceptors, factories, dependency injection and what-not on top of each other are infamous for that.
- pjmlp 2y ago
- ChrisArchitect 2y agoRelated: Java 23 https://news.ycombinator.com/item?id=41567728 https://news.ycombinator.com/item?id=41567728
- tstrimple 2y agoI feel for the enterprise Java devs. Doesn’t matter how good the language becomes and what shiny new features it gets, they are forever tied to a version 20 years out of date. Working with a client right now with dozens to close to a hundred Java 8 apps still being maintained.