3 ms·
This rant is at least ten years out of date, and is at this point entirely unimaginative. More importantly it does not represent where JS ecosystem efforts have
by cqqxo4zV46cp 3y ago
This rant is at least ten years out of date, and is at this point entirely unimaginative. More importantly it does not represent where JS ecosystem efforts have been going for 3-5 years. My personal site is built with a JS framework. It’s sent to the client as ‘static’ HTML and CSS. A JS payload is also sent to power (optional) client-side-interactive functionality (e.g. the “copy” button on code snippet blocks).
Meanwhile, I get to use what is easily the best ecosystem of (lowercase) web component / templating tools, hands down. I’ve used more templating tools than I can count, and nothing compares to Vue SFCs, Svelte, or hell, even JSX as much as I loathe it.
I’m a fairly oldschool do-it-in-notepad web developer, not some kid that grew up on JavaScript. I’ve been deeply, deeply skeptical of and hesitant to employ JS-ecosystem tools. The recent work around fairly seamless isomorphic development is slowly but surely winning me over. It’s increasingly addressing my concerns re accessibility, performance, reliability, semantics, ‘letting the browser do what it does best’, etc. All things I deeply, deeply care about, and all things that caused me to rail against JavaScript in the past.
- peterkonsz 3y agoThe JS ecosystem of 2024 does not represent what's on the web right now. What is out there is by-and-large codebases that were started in the mid 2010s. Sure, frameworks have been doing a great job correcting mistakes over the past couple years, but the JS-heavy junk of the 2010s is still largely out there ruining access for folks.
- racked 3y agoSo what _does_ represent what's on the web right now? Genuinely curious to learn.