Day 243 of TypeScript/JS Only:
switching back to #Golang 🤦♂️
I explored the toolchain, gave everything a good workout, compared alternatives, runtimes, potential CICD workflows… tsc, esbuild, deno..
When it all works, it’s ok. Janky and kludgy, but it works. When it doesn’t work: GOOD FUCKING LUCK OMFG 🤡 🌎
Good to have types, and not be working in JS, but there’s so much indirection it’s a house of cards with more hidden cost and risk than my 🧠 can tolerate
GM
Yesterday I rewrote 80% of this code in Go in just a few hours, deployed and functional, ready to finish today.
VS. months of TypeScript/JS shenanigans using and testing string.replace() in tsc and jest, then deno and esbuild … 😭 tests pass locally but once transpired into JS and deployed it’s non-functional, even with the literal same input, even though the JS looks good …. 🤷♂️
Suspect runtimes, definite path ahead to finish isolating this but … my concern here is the investment in time required to diagnose and investigate what should be simple issues to replicate and solve.
Do I need separate tests for the TS and also the resulting JS? 😆
I deliberately stuck with this, as it’s a long-running concern and I wanted to really explore this - WTH am I missing?!? Iterated all through the toolchain, different transpilers and runtimes, the latest IaC and shiny modern frameworks, Promises, tests .. all looked great until it hit prod 💥 🤬
deno is a start, but the entire ecosystem is just too risky to invest in IMHO
(╯°□°)╯︵ ┻━┻ 🤣
