Java 21 makes me like Java again

Post by kaba0 » Sun, Sep 17, 2023, 9:57 AM UTC

troupo wrote: post #329

kryptonomist wrote: post #312

Earlier quoted context omitted.

Go almost instant build time is a huge productivity boost when compared to Java. You get both the solidity of a typed language, and the development speed of interpreted languages (py, js).

Java's build times are very fast. Java's build tools are anything but. And I'm surprised no one is doing anything about it.

Post by winter_blue » Sun, Sep 17, 2023, 10:00 AM UTC

pjmlp wrote: post #429

neonsunset wrote: post #417

Earlier quoted context omitted.

Why async/await is not a good thing? What makes green threads better? Do you know the difference, the issues async/await addresses that green threads simply do not?

Read David Fowler's guidelines.

Post by kaba0 » Sun, Sep 17, 2023, 10:07 AM UTC

zelphirkalt wrote: post #435

mrkeen wrote: post #360

Earlier quoted context omitted.

> the sane members of the Java community have long since moved on from Java, and they're not coming back We wish! We're stuck in the Java job market, reading Java praise pieces like this... Oh boy! Java's getting structs?

How long until we get continuations in Java? Maybe another 10y? How long until we get TCO? Lets say 20y? And in the end it will still not feel clean or as neat as other languages, that had this stuff for multiple decades.

Post by kaba0 » Sun, Sep 17, 2023, 10:08 AM UTC

bedobi wrote: post #202

wayfinder wrote: post #106

Earlier quoted context omitted.

Well when Sun imploded and Oracle stepped in, Java stopped getting regular releases for 10 years. Java versions literally came out every 2 years before Oracle happened. So that’s why they’re 10 years behind. But now they come out like 2+ times a year so they’re on track making major progress. Also the null thing hasn’t been an issue for over 10 years. Just use null annotations and both your static checker and your ID…

> Also the null thing hasn’t been an issue for over 10 years. I don't think I've ever seen a Java codebase that doesn't experience NPEs in prod, and that includes modern greenfield ones that make use of all the tools to combat it. > Just use null annotations and both your static checker and your IDE will catch every NPE. Yeah, or just catch it in code review, or just xyz... Or, just switch to a compiler that doesn't…

Post by mike_hearn » Sun, Sep 17, 2023, 10:15 AM UTC

insanitybit wrote: post #79

northern-lights wrote: post #31

The biggest feature in Java 21 is the release of Virtual Threads: https://openjdk.org/jeps/444 For some reason, this is missing from the article. If there was any feature that would sway existing Golang developers to switch to Java, it would be this. It would perhaps also convince the haters of the reactive-style concurrency patterns.

`Executor.newVirtualThreadPerTaskExecutor` versus `go` really gets to the heart of why I think that Go developers aren't going to be switching. edit: Sorry, it's actually: try (var executor = Executors.newVirtualThreadPerTaskExecutor()) { executor.submit(...) ) instead of `go`

    fun  go(body: ExecutorService.() -> T): T =
        Executors
            .newVirtualThreadPerTaskExecutor()
            .use(body)

    val result = go {
       val result1 = submit { slowOp() }
       val result2 = submit { blockingOp() }
       result1.get() + result2.get()
    }

    class Shortcuts {
        static  R go(Function task) throws RuntimeException {
            try (....) { return task.apply(service) }
        }
    }

    var result = go(service -> {
        var result1 = service.submit(() -> slowOp());
        var result2 = service.submit(() -> blockingOp());
        result1.get() + result2.get();
    });