Knock knock Who's there? long pause Java
High Speed Trading team using Java looking puzzled .... https://lmax-exchange.github.io/disruptor/
This thing is a-ma-zing. It is truly a wonder. It is something to behold. The "Disruptor" pattern.-
Java 27
21–30 of 423 posts
Re: Java 27
#22Serious question: when should one use Java for greenfield projects in 2026?
Jruby is nice - runs Ruby on a Java Virtual Machine with full concurrency and Ahead Of Time compilation
Re: Java 27
#23Re: Java 27
#24Serious question: when should one use Java for greenfield projects in 2026?
When you work at a Java shop. Kotlin is much nicer if you have to run on the JVM but aren't restricted to Java.
Re: Java 27
#25Re: Java 27
#26Serious question: when should one use Java for greenfield projects in 2026?
When building boring web applications with a sizeable team that need to run for a long time. Hiring developers is easy since there are many, there is nearly no magic and the language is quite strict and type safe so it works well with a large team.
And that "team" nowadays may also consist of many AI agents. In my experience Claude Code for example works very well with a typed, slightly boring language with lots of framework and library support. Because it doesn't compile when you get something wrong, instead of getting a vague runtime issue that Claude can't always see.
Re: Java 27
#27Serious question: when should one use Java for greenfield projects in 2026?
[deleted]
Re: Java 27
#28C# dev here: it’s amazing how different this is from a Microsoft release. First off, Oracle are doing versions at approximately twice the cadence. But also, and I’m guessing this is a function of the much larger Java audience: things rarely get two preview versions in a proper release. Updates in beta versions, yes, all the time. It also feels like Microsoft are bundling a lot more into the platform and leaving less…
razzmatazz? Do you mean marketing lies and self aggrandizement for merely doing shoddy work?
Re: Java 27
#29C# dev here: it’s amazing how different this is from a Microsoft release. First off, Oracle are doing versions at approximately twice the cadence. But also, and I’m guessing this is a function of the much larger Java audience: things rarely get two preview versions in a proper release. Updates in beta versions, yes, all the time. It also feels like Microsoft are bundling a lot more into the platform and leaving less…
> First off, Oracle are doing versions at approximately twice the cadence Is that actually a good thing? But Oracle started playing a game, for better or worse, where they decided to couple the "language version" with a single specific runtime's release schedule. For example, in "Java 27" there are exactly 0 language changes and 1 minor feature addition to the TLS library. Everything else is OpenJDK runtime internals…
You’re only counting JEPs, which are only for more involved features. There are lots of changes to the JDK apis that are used by other runtimes. See, for instance: https://javaalmanac.io/jdk/27/apidiff/26/.
Admittedly, the terminology here is almost designed to be maximally confusing, and I’ve never read a good post that laid out how everything relates.
Re: Java 27
#30Earlier quoted context omitted.
When you think a garbage collected language is a good fit for whatever you're building?
Wouldn't you go with golang in that case?
Golang gives you none of nice features of a modern language while being about the same performance tier as Scala or Java, so there's basically no reason not to use Scala.