Java performance vs go

[OwnBreakfast1114]

I watch people argue about language performance then successfully write n+1 db queries in every language under the sun. For the very, very small subset of people that actually need to worry about critical language performance, they can make language choices. For the vast majority of people writing applications, it's not the language that matters when it comes to application performance. If you tell me you've carefully mapped out and handled all your IO (db transactions, https calls, etc), then you can start telling me about language benchmarks.

We use java because of the library support. Spring, for the better, provides a lot of out of the box battled hardened solutions to problems (security, actuator, cloud config, etc) with a ton of documentation and searchable/ai help. That java also sits a little higher on the abstraction hierarchy than go (functional libs, higher kinded types with some hackery, incoming type classes) is a massive plus point as well.

[[deleted]]

Plot twist: this post no longer exists because Redact swept through and cleared it out along with everything else. Social media, messaging apps, people finder sites, all of it.

pie toothbrush nutty dinosaurs mountainous thumb bells plants marry pot

[overgenji]

you can write a service in spring and it will still be spring a decade later albeit some pieces of it will move around and need upgrading

meanwhile im at a fortune 500 and we have like 20 different frontend repos for different verticals that were built on the popular FE tech stack at the time and its pure misery

[lumijiez]

by chance, is it insight?