“Going Buildless | Max Böck”
https://mxb.dev/blog/buildless/
I've gone buildless for personal projects for a long while now and am not going back
Also on HTML includes: it makes me sad to think that XML had standardised includes almost 20 years ago. I wasn't a fan of XML at the time but in hindsight it's looking like we, web devs, dumped an entire ecosystem of tools and standards just out of an annoyance with error handling that we then got a worse version of anyway with JSX, setting us back a decade
Now the XML paths in browsers are barely maintained. Module JS in SVG, for example, basically doesn’t work. I encounter weird bugs in every browser’s SVG implementation any time I try to load a non-trivial illustration. I would actually love to be able to use XHTML occasionally for project where semantic extension made sense or where interop with EPUB was a plus. 🤷🏻♂️
Lady, EVOLVED 
@baldur i use XHTML for basically everything personally, because “keep the data in XML and transform to XHTML” is a trivial operation (with XSLT; you can even deliver the data in its original form to the user and have their browser do the transformation if you want), and MUCH better than the more contemporary “keep the data in JSON/YAML and use a heavyweight build step written in NodeJS or Ruby to transform it to HTML”
but
yeah, module scripts (<script type="module">) still don’t have support in Webkit and maybe Blink in XML documents, and it is a real thorn in my side
@baldur anyway, putting blame where it is deserved, it’s actually Mozilla and Opera and WHATWG who killed XML by saying “actually just HTML and JS, the things we are already dominant market players for, is fine and all anybody really needs”
and in terms of Mozilla, probably specifically Brendan Eich, as i understand