Java 21 makes me like Java again

Post by mdhb » Sun, Sep 17, 2023, 1:12 PM UTC

lakomen wrote: post #530

mdhb wrote: post #525

Earlier quoted context omitted.

I never see Dart talked about in these contexts but just to highlight a few things. 1. Compiles to native code with a single and very reasonable sized binary on pretty much any platform. 2. Compile to WASM (coming this year) if that’s your thing. 3. Excellent concurrency support with lightweight and simple mental models 4. Variables are not nullable by default thus simplifying tedious checking in your codebase. 5. Sy…

Performance matters. Dart isn't even in the same league. And its null handling and checking is the worst. I absolutely hate it. Java over Dart any day.

Post by sgt » Sun, Sep 17, 2023, 1:18 PM UTC

impulser_ wrote: post #187

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.

I don't think any existing Go developer is going back to Java. I worked with Java for 10 years and switched to Go and I will never go back. This is mostly because applications and libraries are so hard to reason about and understand due to inheritance, packaging, OOP, build tools ect compared to Go. Go is simple. It's easy to understand, read, and maintain. The packaging is like how you would package files on your co…

Post by boxed » Sun, Sep 17, 2023, 1:21 PM UTC

lakomen wrote: post #538

The biggest problem with Java is... the walled garden, the snob society, the elitist, exclusive culture. Go isn't like that, or at least wasn't when G+ was still around. Nowadays I don't get in touch much with people, but when I create issues Go people are usually not as unfriendly as Java/JVM people.

Post by tomp » Sun, Sep 17, 2023, 1:22 PM UTC

neonsunset wrote: post #417

kaba0 wrote: post #385

Earlier quoted context omitted.

You can’t decide language superiority by the number of features. While C# indeed has many cool features, I do think it has already went into C++ territory where all the different, independently cool features have very non-trivial interactions that make it very hard to reason about. Also, async-await is not a good thing — virtual threads are superior in every way in case of a managed language.

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?

  async fn read_file(filename):
    f = await os.open(filename)
    let data = f.read()
    await f.close()
    return data

  fn read_file(filename):
    f = os.open(filename)
    let data = f.read()
    f.close()
    return data

Post by tuyguntn » Sun, Sep 17, 2023, 1:25 PM UTC

kaba0 wrote: post #195

impulser_ wrote: post #187

Earlier quoted context omitted.

I don't think any existing Go developer is going back to Java. I worked with Java for 10 years and switched to Go and I will never go back. This is mostly because applications and libraries are so hard to reason about and understand due to inheritance, packaging, OOP, build tools ect compared to Go. Go is simple. It's easy to understand, read, and maintain. The packaging is like how you would package files on your co…

> This is mostly because applications and libraries are so hard to reason about and understand due to inheritance, packaging, OOP, build tools ect compared to Go. You are just at the early phase of the project. > Go is simple. It's easy to understand, read, and maintain My opinion is that Go is too simple, to the point that it hinders understanding and readability. 4 nested loops with random mutability is much worse…