Ever since that first Netscape Navigator 2.0 release, I’ve been a #JavaScript sceptic.
I’ve long suspected my brain is simply incompatible with this level of ambiguity, which is saying something as I worked with (and loved!) dynamically typed languages and runtime meta-class design 🤷♂️
As a Backend Engineer I’d been avoiding it like the plague, but year after year it’s popularity only grew, eventually taking over FullStack then Apps, then Infra and now Platform!?! 😱
I kept trying it, year after year: hated it. Eventually did a fair bit of paid work in Node, Vue and React: still hated it.
So …. 8 months ago I forced myself to switch to #TypeScript /JS full-time, to try and figure out just what my brain is having trouble with, why do I (and only I?) hit so many random toolchain and IDE issues, random corruptions, dependency cycles from hell, etc. ???
I’ve now spent 6-8 weeks trying to get a simple string.replace(//) to not just work locally and in all of my tests, but now that I’m deploying it to prod it also needs to work when invoked as a node22js Lambda!! 😂🤣😭
Gotta be async shenanigans (am I not already waiting for every Promise?) but OMG every time I fix one thing something else breaks, or cache corrupts, or IDE starts misbehaving… now I’ve migrated to deno and esbuild from tsc and have new issues on top of the old ones 🎉
I’m so glad I did this, for so many reasons both personal and professional, but Imma look into that WASM PoC next … I miss #Golang ! 🫂