82
this post was submitted on 05 Dec 2025
82 points (100.0% liked)
technology
24258 readers
111 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
that's technically still true about most of nodejs's direct competitors, even today. it ends up being hugely faster (per CPU) if most of your request is waiting on the database/filesystem/etc. It's not faster if each request needs to hog the CPU, which is uncommon for what people normally use nodejs for. golang is probably the only mainstream competitor that is likely to do a better job at this one specific task. Everything else either has half-assed or non-existent support for async IO (python, php, ruby) or is very clearly not a direct competitor to nodejs (e.g. rust, zig, c) or I refuse to acknowledge it exists for lovecraftian reasons (Java).
The JVM is a pathway to abilities that many would consider... Unnatural. And quite honestly, the language has gotten less terrible over the past several years. The problem is that a good chunk of the software out there in the corpo world is still stuck on Java 8 and can't migrate to 17/21/etc. without modifications and a fuckton of testing, and companies will drag their feet to avoid that amount of time and effort. But yeah, starting around Java 21 or so, they're basically backporting random Kotlin features into the main language. But if you're maintaining legacy JEE apps for something like WebLogic? Good fuckin' luck. And good fuckin' luck explaining Spring Boot to boomers.
...I'd still rather be working with Kotlin, though. (Currently trapped in Java 8 hell, and hopefully getting my team's main codebase up to Java 17 spec in a couple of weeks because a vendor is demanding it.)