Incoming rant: I’ve had to do more hands-on hydration work as I explore static site generators and I’m just deeply unhappy with the state of front end tooling. I now have a taste for
* directory based routing and opinionated defaults that give you the basics to string together html pages with reusable partials and be production ready in minutes (think rails)
* postcss (css tooling)
* reusable and compostable components
* hmr-style dx
* serverside generated pages, as inlined as possible — fastest experience for end user, avoids js if not needed
* not having to think how and where css or images get compiled
Vitejs looked headed that way but recenty dove into it and… it ain’t it yet. Getting something to render on a server then “turn on” with react in the browser is not straightforward.
Remember how much sense $(document).ready() made? Hydration should be that easy and it is not.
* directory based routing and opinionated defaults that give you the basics to string together html pages with reusable partials and be production ready in minutes (think rails)
* postcss (css tooling)
* reusable and compostable components
* hmr-style dx
* serverside generated pages, as inlined as possible — fastest experience for end user, avoids js if not needed
* not having to think how and where css or images get compiled
Vitejs looked headed that way but recenty dove into it and… it ain’t it yet. Getting something to render on a server then “turn on” with react in the browser is not straightforward.
Remember how much sense $(document).ready() made? Hydration should be that easy and it is not.