When nodejs became a thing and everyone started yapping about mongodb and their magical non blocking event loop language I felt like I had died and gone to hell. The fact that almost every single developer i then would interact with trying to convince me that anything that wasn’t nodejs could only handle 1 request at a time sent me over the edge. Then everyone started calling themselves a full stack developer and thinking their stupid little crud wank app was gonna be the next google so it absolutely must be written in nodejs. Npm toolchain still the absolute worst ive ever used and almost every setup used nodegyp which when forced to work on windows made me rather be destitute than install visual studio just for the build tools to not work and be left staring at meaningless npm errors. I dont think ive ever successfully got it to build on windows once in the last 10 years ive had to use this shit. Thank the lord for docker, oh wait my organisation doesnt let me use docker
Snorting a line of react native every morning i love having my ui dependent on some javascript translation layer wowie thanks facebook for your resource destroying memory leaking garbage shit that somehow became industry standard everywhere
anything that wasn’t nodejs could only handle 1 request at a time
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).
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.)
When nodejs became a thing and everyone started yapping about mongodb and their magical non blocking event loop language I felt like I had died and gone to hell. The fact that almost every single developer i then would interact with trying to convince me that anything that wasn’t nodejs could only handle 1 request at a time sent me over the edge. Then everyone started calling themselves a full stack developer and thinking their stupid little crud wank app was gonna be the next google so it absolutely must be written in nodejs. Npm toolchain still the absolute worst ive ever used and almost every setup used nodegyp which when forced to work on windows made me rather be destitute than install visual studio just for the build tools to not work and be left staring at meaningless npm errors. I dont think ive ever successfully got it to build on windows once in the last 10 years ive had to use this shit. Thank the lord for docker, oh wait my organisation doesnt let me use docker
Snorting a line of react native every morning i love having my ui dependent on some javascript translation layer wowie thanks facebook for your resource destroying memory leaking garbage shit that somehow became industry standard everywhere
ahhh i love a good rant. even though i don’t understand most of these words I got so angry for you
i met an engineer at FB and she reported that FB doesn’t even use very much react native for their own apps lul
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.)