3 ms·

Java is not ahead of Go, they're on part but often Go is faster while using 2-10x less memory. Value type makes optimization much easier in Go. The fact that y

by Thaxll 1y ago

Java is not ahead of Go, they're on part but often Go is faster while using 2-10x less memory. Value type makes optimization much easier in Go. The fact that you specifically mention Go explains a lot. btw c# is faster than Java, so not third place, it's more a 5th~ https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/javavm-go.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

999900000999 1y ago
Doing what? Benchmarks aren’t all that useful since usually the bottleneck is File IO, external api calls, db calls, user latency or a combo of the 4. Go’s main advantage in this matchup would be conciseness. Go code looks so clean and nice, Java doesn’t. I personally don’t care for Java, but I have bills so it’s always in my back pocket. Things happen , sometimes you need to write Java to eat. “Fred, you really should just take the job.” “Martha you don’t understand, it’s Java with an Oracle DB.” “Fred, I know it’s bad, I know you still have nightmares about the 4 types of string in Java 8, but it’s not just us now.” With a tear in his eye , fear in his heart. “Martha, if I must… I’ll open Eclipse once more.”
- vips7L 1y ago
  Go code is far from concise. Java is more expressive than Go in almost every way.
- noisy_boy 1y ago
  > I personally don’t care for Java, but I have bills so it’s always in my back pocket. Things happen , sometimes you need to write Java to eat. I write Java to pay bills and my eyes and fingers thank me everyday for sparing them from a sea of if err != nil. I won't even go(!) into the iota stupidly compared to Java's enums.
  - 999900000999 1y ago
    I want to like Go. I built a small phone app with it. The best way to describe it is incomplete. I think the philosophy is to make things more minimal? A lot of frameworks don’t exactly do everything they need to. I’ll still pick it over Rust, which seems to like punishing the developer.
    - noisy_boy 1y ago
      I wrote an application in Go about couple of years ago that is still running in production without much maintenance. The language isn't bad as such + the single binaries are nice. But until they reduce the error handling noise (which I suspect they never will), I won't choose it voluntarily to write code. Rust is actually nice if one can accept cloning as a workaround. The error handling via ? is awesome in rust.

by Thaxll 1y ago

999900000999 1y ago

Doing what? Benchmarks aren’t all that useful since usually the bottleneck is File IO, external api calls, db calls, user latency or a combo of the 4. Go’s main advantage in this matchup would be conciseness. Go code looks so clean and nice, Java doesn’t. I personally don’t care for Java, but I have bills so it’s always in my back pocket. Things happen , sometimes you need to write Java to eat. “Fred, you really should just take the job.” “Martha you don’t understand, it’s Java with an Oracle DB.” “Fred, I know it’s bad, I know you still have nightmares about the 4 types of string in Java 8, but it’s not just us now.” With a tear in his eye , fear in his heart. “Martha, if I must… I’ll open Eclipse once more.”

vips7L 1y ago
Go code is far from concise. Java is more expressive than Go in almost every way.
noisy_boy 1y ago
> I personally don’t care for Java, but I have bills so it’s always in my back pocket. Things happen , sometimes you need to write Java to eat. I write Java to pay bills and my eyes and fingers thank me everyday for sparing them from a sea of if err != nil. I won't even go(!) into the iota stupidly compared to Java's enums.
- 999900000999 1y ago
  I want to like Go. I built a small phone app with it. The best way to describe it is incomplete. I think the philosophy is to make things more minimal? A lot of frameworks don’t exactly do everything they need to. I’ll still pick it over Rust, which seems to like punishing the developer.
  - noisy_boy 1y ago
    I wrote an application in Go about couple of years ago that is still running in production without much maintenance. The language isn't bad as such + the single binaries are nice. But until they reduce the error handling noise (which I suspect they never will), I won't choose it voluntarily to write code. Rust is actually nice if one can accept cloning as a workaround. The error handling via ? is awesome in rust.