Did a quick check around out of courtesy, no activity past 2015. Hoping for the best

Wondered the same thing several times in last few years.

I'm just watching the release live stream on youtube, in the background. Interesting stuff!

@U11EL3P9U got a link to the livestream?

Certainly

I believe Brian Goetz is popping up later to talk about the changes.

Thank you! 🙏

Some caveats when using virtual threads with Clojure listed in https://www.reddit.com/r/Clojure/comments/16lq5gr/clojure_virtual_threads_with_ring_and_jettyhttpkit/

And https://clojure.atlassian.net/browse/CLJ-2771

Excellent news. I'll be migrating to Java 21 LTS version over the winter holidays and updating all the Practicalli content to use Java 21 as the recommended version if all goes well. Not expecting any code changes, but lots of testing to make sure 😆

Newbie here. Does anyone wait until it’s published to homebrew?

% brew search openjdk
==> Formulae
openjdk ✔             openjdk@11 ✔          openjdk@17 ✔          openjdk@8             openj9                openvdb

I downloaded a prebuilt version from the link above and installed it with SDKMAN (https://sdkman.io/usage#localversion)

I'm also an SDKMAN user and am usually happy to wait until they make a new release available.

Do jenv and sdkman play well together?

I think they are different solutions to the same problem. If you have jenv, you can use that.

For example, with sdkman: sdk install java openjdk-21-lcl ~/Downloads/jdk-21.jdk/Contents/Home sdk use java openjdk-21-lcl

I usually wait about 3 months after a new major relase as there is usually a new point release by then and all the ways of installing java have been updated I've used jenv for commercial projects, especially useful if a project needs a special version of java (I e to support niche persistence drivers) Otherwise I would only have one Java version installed

@U05254DQM that seems like a very sane strategy! I tend to install new SDKs when they become available because I need to test if they work with the OSS libraries and tools I maintain. So I tend to have a bunch of SDKs installed via SDKMAN. This also helps me with support when I need to reproduce an issue a user is having. And, for me, SDKMAN provides a nice way to switch to the GraalVM SDK when I'm doing GraalVM work.

We're on 20.0.2 in production right now and will probably roll up to 21 as soon as the Temurin builds are available.

We’re using Coretto, basically the same strategy.

@UE21H2HHD the 'sane' strategy is usually applied to most things software related (and sometimes hardware). However, if I were a maintainer off OSS projects like yourself and Sean (and many others) then I would be testing the various versions of Java releases. My great thanks to every maintainer that does this important work. I tend to be more conservative for commercial work, especially with the JVM (as there are usually many other challenges to solve 😄 )

Brian Goetz presenting now on the live stream and all new directions feel very Clojure inspired

We're on 20 as well on production 🙂 and we'll go to 21 when temurin is out too 🙂

@U04V70XH6 or @U11EL3P9U : Just curious, why wait for temurin? Is it a license issue?

Most just comes down to promoting diversity and showing support for other providers - we do look at others too, like Amazon Coretto from time to time (perhaps we should revisit that soon)

Yup, mostly that. We've gotten used to using the Temurin builds at this point and it's become our default across all tiers.

Ah ok, thanks!

And, on delightful occasion, https://developer.ibm.com/languages/java/semeru-runtimes/ (f/k/a Adoptium J9) (f/k/a IBM J9)... if for no other reason, then because when HotSpot dumps core, you want an alternative that isn't just a rebuild. Edit: To be clear, Semuru is the name of the binary build, akin to Temurin; the contents of a Semuru package are OpenJDK and OpenJ9.

don't wanna be productive, just wanna read about productivity

I’m training myself to ignore these kinds of articles when they pop up on the RSS feed.

It only makes sense if you think of your website in terms of "users" or more specifically "potential ad clickers" rather than "readers." Produce the maximum amount of ad space for the least effort, rather than something people want to read. see also: everything written with the help of AI.

Specifically for http://planet.clojure.in's method of aggregating articles, those long ones make it annoying to find the next article after that one.

Is there a summary on how to be productive I am now using Neovim, so it seems I have several of the stories covered already... and at least one on using i3 window manager which I already use. The only lesson I am learning on productivity is not to read the rest of this article 😢

I have sent an email to the http://planet.clojure.in creators suggesting removing Hackernoon from their collection, or somehow limiting the size of the content included in the http://planet.clojure.in page

Only an 87 minute read. Sounds like a productive use of time

SEO boost attempts