Alternately, you can just stick close to standards and not really worry about it. I write plain CSS. I use Web Components as my unit of isolation, generally s

Alternately, you can just stick close to standards and not really worry about it. I write plain CSS. I use Web Components as my unit of isolation, generally sticking with the light dom. I have a small state utility [1] that I wrote years ago and works great. I do have a build step before deployment, but I use vite during development so I have zero "make a change, wait, test, rinse, repeat" downtime. When it's time to deploy, vite build does the trick nicely. I don't use frameworks. I don't use JSX. I don't use typescript, for types I use jsdoc in vscode which gives me 90% of the benefits of TS without the downsides. My pages are light, fast and easy to maintain. I don't have to deal with painful build steps, or framework churn. Debugging is simple. No multiple layers of transforms and sourcemaps, WYSIWYG. I'm pretty passionate about the "keep it simple" philosophy. I chose to innovate in the problem domain, not the technical one. Anecdotally, I had a new developer join my team and he was initially very confused. He said "it's just so strange using this tech stack. You make a change, and you see it..." I didn't know whether to laugh or cry. [1] https://www.npmjs.com/package/applicationstate https://www.npmjs.com/package/applicationstate