Harry Roberts🌐 If you’re going to build for the web, build *on* the web.
If I was only able to give one bit of advice to any company: iterate quickly on a slow-moving platform.
In the last year alone, I have seen two completely different clients in two completely different industries sink months and months into framework upgrades. Tens, if not hundreds, of thousands of dollars rewriting entire projects just to maintain feature parity with the previous iteration. This is not meaningful or productive work—it is time sunk into just keeping themselves at square one. A form of open-source vendor lock-in.
Jasper@csswizardry I am going through this now, as a small agency with quite a few active clients (ranging in _how_ active, but still active) and we basically have 3 states: gulp (moving away from this), webpack (we can mostly stay because it still upgrades OK but…), and vite (new hotness, but for how long?!)
I want to go back to a world where we write CSS and JavaScript and maybe have something like Vite but only for hot-reloads. All transpiling and post-processing ends up kicking your ass.