Deno Fresh pushing "islands" is a huge negative... but that's to be expected when Vercel's VC enforcers are behind it. 99% of the React ecosystem does not func

Deno Fresh pushing "islands" is a huge negative... but that's to be expected when Vercel's VC enforcers are behind it. 99% of the React ecosystem does not function without reactivity enabled: it's literally in the name. As a result most applications written in React depend heavily on interactivity. The only category that is an exception is ecommerce where you're normally pulling from a CMS... and Vercel needed to fight Shopify for that space so they went and "helped" the React team turn the framework into something it's not with RSC. _ Also most of your complaints aren't at all addressed by Deno? It uses an amount of magic closer to current Next.js than pages-era. It actually removes some conventions for separation that Next.js has (all routes potentially being api routes for example). And as far as I can tell both libraries expect you to explicitly handle errors during data fetching (and your users would probably appreciate that too) _ One of these days I might get annoyed enough to fork Next.js 1.0, sprinkle in a folder router for express and call it a day on a framework that doesn't fight React and just stays out of my way.