My favourite is "all the boilerplate" then they come up with go's error checking where you repeat the same three lines after every function call so that 60% of your code is the same lines orlf error checking over and over

[–] [email protected] 4 points 8 months ago

Things like lombok make the boilerplate less of an issue in modern Java too

[–] [email protected] 2 points 8 months ago (1 children)

And god help you if you forget those 3 lines somewhere and you silently have database failures or something else.

[–] [email protected] 2 points 8 months ago

Yeah, that's the other thing - it does become easier to accidentally fail to deal with errors and the go adherents say they do all of that verbose BS to make error handling more robust. I actually like go, but there's so much BS with ignoring the pain points in the language.

[–] [email protected] 1 points 8 months ago (1 children)

When you handle all your errs the same way, I'd say you're doing something wrong. You can build some pretty strong err trace wrapping errs. I also think it's more readable than the average try catch block.

[–] [email protected] 2 points 8 months ago

You still need to add error handling to every call to every function that might raise an error

[–] [email protected] 13 points 8 months ago (2 children)

Those who say such things are straight ignorant

[–] [email protected] 9 points 8 months ago (1 children)

They’re basically fashion victims.

[–] [email protected] 6 points 8 months ago

I wouldn't say so. They are inexperienced. They don't know where the bottleneck of most of the modern software is (it's io in 80-90% of cases) and how to optimize software without rewriting it to C++

[–] [email protected] -4 points 8 months ago* (last edited 8 months ago) (2 children)

How are they ignorant? It’s a known fact that java is slow, at least slower than some others. Sure, it’s still fast enough for 95% of use cases, but most code will run faster if written in, say, C. Will have 10x the amount of code and twice as many bugs though.

[–] [email protected] 3 points 8 months ago* (last edited 8 months ago) (1 children)

Java is indeed slower than C, Rust, in some cases than Go.

But that doesn't mean that

code will run faster if written in, say, C

Again, like 80-90% of production code are bounded by disk/network io operations. You will gain performance from using C in embedded systems and in heavy calculations (games, trading, simulations) only.

[–] [email protected] 0 points 8 months ago

Which is exaxtly what I said, that it’s fast enough for most use cases.

In theory though, you will “gain performance” by rewriting it (well) in C for literally anything. Even if it’s disk/io, the actual time spent in your code will be lower, while the time spent in kernel mode will be just as long.

For example, you are running a server which reads files and returns data based on said files. The act of reading the file won’t be much faster, but if written in C, your parsers and actual logic behind what to do with the file will be.

But it’s as you said, this actual tiny performance gain isn’t worth it over development/resource cost most of the time.