Post

Was hoping you'll turn this one linked post into something real. 💯

Let me guess, were those clients upgrading to the Next.js App Router? Gone through this exact migration path 3 times now — never again

This is a surprisingly difficult message to get across today. One approach I tried was to encourage thinking in 20 year increments. In the next 20 year cycle, how much time do you want to devote to fixing/speedingup/updating/replacing your front end frame work?

I‘m planning to migrate some Angular SPAs to more „bare bones“ tech, but not sure if I can get by with just plain JS or if it‘s too cumbersome. I‘m thinking maybe TS for type safety and htmx for navigation/DOM replacement. Do you have a recommended stack?

We seem to live in a world where every new hire brings a new framework. I shouldn't complain as untangling overcomplicated builds has kept me employed for the best part of 28 years, but I take no pleasure seeing peoples pain trying to manage these projects.

Agreed. For me it's the excellent experience of the dev-server proxy I get when I work on a Vue SPA. Having my changes to components and CSS reflected immediately after I save is fantastic. This from @chriscoyier.net comes to mind (chriscoyier.net/2024/11/07/d...)

I also wrote about this idea - where being leaner is a good long-term strategy shane-o.dev/articles/int...

Good read. Even without doing a lot of the “fancy” things you mentioned (page transitions), the (react) upgrade cycle is a bear across our many micro frontends. Ultimately our refactors have been a net benefit, but the npm ecosystem + renovate bots means constant maintenance PR’s.

Agreed. And my advice there is generally ‘make decisions you can easily change or undo’. You don’t need to have all the answers now, but you do need to remain adaptable.