Outshining JS in the backend is not an achievement.
this post was submitted on 16 Apr 2025
19 points (88.0% liked)
Programming Circlejerk
182 readers
2 users here now
Community to talk about enlightened programming takes
Rules:
- read and follow the programming.dev code of conduct
- no flamewars
- mark your unjerks
- only programming related content allowed
- link to the original source
- do not mention this community in places like hackernews, lobste.rs, or the general programming communities on Lemmy where we source jerk material from.
founded 3 months ago
MODERATORS
Go is like the kid who gets held back for a year every year in school, but feels very proud every time he manages to beat up a fellow performance kindergartner, like JS or Python.
I like go but I don’t like evangelists
I like Go, but I also like only having to write Typescript for everything. Performance is not really a problem when 99% of web applications are just networking plumbing with simple business logic over a data store. If you really need performance, split it into a dedicated service written in C, C++, or Rust that does that one critical thing really fast.
I haven't looked at any performance comparisons, but better performance also generally means lower resource usage aka lower costs aka less electricity use aka all the positive effects of using less electricity.
Just imagine if the entire industry cared about efficiency and used more efficient runtimes. How much less power would be used in aggregate? ... one can dream....
Higher level language abstractions still run on top of efficient lower level engines. Python doesn't run on Python. Node.js runs script code in V8 which is a C++ engine. Typically, the plumbing heavy lifting is done by the lower level code via API calls, and the business logic layer on top is comparatively lightweight.
Of course, a developer could eschew those conventions. But I wouldn't feel comfortable shipping a video encoder written in something like Python, or even a mid-level abstraction language like Java or Go.
ignore nulls, ignore race conditions, choose go
#WebVibin' #HumoriestDev #DockerFiddler
I work in go currently (and a laundry list of languages in the two decades prior). It's not perfect, but I generally like it as a backend guy doing various things.
I like GoLang and loath JavaScript, but don't complain about Node pulling in 42 external libraries when GoLang is pulling in 32 external libraries (and using an additional 10 bundled with the compiler).
Based.