4 ms·

> ... even a shit one like Java. I agree with your point about Go enums. But in defense of Java, modern Java is actually pretty pleasant. Virtual threads, re

> ... even a shit one like Java. I agree with your point about Go enums. But in defense of Java, modern Java is actually pretty pleasant. Virtual threads, records and sealed classes, pattern matching, state-of-the-art garbage collectors, a great standard library etc. (and obviously well-behaved enums). Not to mention the other languages you get for free with the JVM ecosystem. It might not be as expressive as Rust, but certainly Java/JVM > Go.

deleted 2y ago
[deleted]
deleted 2y ago
[deleted]
pjmlp 2y ago
It is so funny how Go folks praise its standard library, when it is a fraction of Python, Java and .NET standard libraries.
- deleted 2y ago
  [deleted]
- kbolino 2y ago
  Things that were in the Go standard library from the first public release (2012): encoding/json vs Python: 2008, json package added in version 2.6 .NET: 2019, System.Text.Json came with .NET Core 3.0 JVM: still nothing net/http client vs Python: gave up, "just use requests" .NET: also 2012, HttpClient came with .NET Framework 4.5 JVM: 2018, HttpClient came with Java 11 The time library definitely sucks though. There's really no excuse for it, joda-time came out a long time ago.
  - pjmlp 2y ago
    Cherry picking examples are we? What about actually counting the set of features across a full stack application? I can pick countless of examples of features in Java and .NET standard library that Go 1.24 still doesn't have any answer for.
    - deleted 2y ago
      [deleted]
    - kbolino 2y ago
      No, I don't think HTTP or JSON are cherry-picked. Depending on what kind of code you write, maybe you haven't needed them as often as I have. Of course, plenty of high-quality third-party libraries exist in the other languages. I've used commons-httpclient and jackson in Java, and everybody and their brother knows about requests in Python (though I prefer aiohttp nowadays). But they are odd omissions from the standard libraries of those languages. At least .NET caught up.

deleted 2y ago

[deleted]

deleted 2y ago

[deleted]

pjmlp 2y ago

It is so funny how Go folks praise its standard library, when it is a fraction of Python, Java and .NET standard libraries.

deleted 2y ago
[deleted]
kbolino 2y ago
Things that were in the Go standard library from the first public release (2012): encoding/json vs Python: 2008, json package added in version 2.6 .NET: 2019, System.Text.Json came with .NET Core 3.0 JVM: still nothing net/http client vs Python: gave up, "just use requests" .NET: also 2012, HttpClient came with .NET Framework 4.5 JVM: 2018, HttpClient came with Java 11 The time library definitely sucks though. There's really no excuse for it, joda-time came out a long time ago.
- pjmlp 2y ago
  Cherry picking examples are we? What about actually counting the set of features across a full stack application? I can pick countless of examples of features in Java and .NET standard library that Go 1.24 still doesn't have any answer for.
  - deleted 2y ago
    [deleted]
  - kbolino 2y ago
    No, I don't think HTTP or JSON are cherry-picked. Depending on what kind of code you write, maybe you haven't needed them as often as I have. Of course, plenty of high-quality third-party libraries exist in the other languages. I've used commons-httpclient and jackson in Java, and everybody and their brother knows about requests in Python (though I prefer aiohttp nowadays). But they are odd omissions from the standard libraries of those languages. At least .NET caught up.