I'm honestly not sure if this is satire or not. > Static was a fun diversion, but we're back to what works. Static works really well for many use cases. And y

I'm honestly not sure if this is satire or not. > Static was a fun diversion, but we're back to what works. Static works really well for many use cases. And you are never going to beat the performance of static in a cache close to your user. I agree that there are many cases where server-rendered is the best option but static with a good sprinkling of JS and server-generated embeds definitely works. > Tailwind CSS is the best thing to ever happen to CSS This is obviously controversial. Maybe for non-static websites where every `<p>` in your site is generated from the same line of code it is trivial to add `class="m-4 text-gray-900"` when I may use the same component in multiple places that gets boring really fast. > GitHub Copilot Maybe if you weren't writing `m-2` on every p this wouldn't be as helpful /s Maybe I haven't seen the light yet, but in most weakly-typed languages Copilot felt like a huge loaded footgun. It also generally worked on the simple cases that didn't require much work anyways. --- I think it is clear that this person found an approach that works for them, but it seems like there is still a lot of from for improvement here.