A drop-in replacement library for a drop-in replacement library for a built-in library that should've worked in the first place. Welcome to the wonderful world of Node.js.

This is why I'm kinda excited about WASM. With a WASM backend for GHC, you can now write almost the entire frontend logic in Haskell, with only some minor bindings on the JS side. I really wish that this happens at some point to eliminate the need for JS almost entirely, but I'm not that hopeful anymore.

Yet, people willingly choose to use one of the most horrific ecosystems out there.

So far I have heard the following explanations for going full-stack JS

• Ability to re-use business logic in back-end and front-end
• Reduced context switching (though with frameworks that's less true)
• You don't have to recruit developers proficient in your back-end language in addition to Javascript

Personally, having worked on a full-stack Typescript project for the past year, I kinda miss the maturity of Java's ecosystem: there is usually one mature and well-maintained library that does its job really well ; while in Javascript-land there are multiple libraries for a single job, each with varying quality and maturity, and most of them are no longer maintained.