Astro vs Svelte

Parent context: What purpose does astro serve if everything is vanilla Reply: Tons! Content collections, components, and layouts all make my workflow and organization much, much simpler while still allowing me the joy and simplicity of writing vanilla code. That's really the gift that is Astro—I get the benefits of a framework but absolutely nothing is any more complicated than I personally want it to be.

Went with Astro deployed to Cloudflare and immensely appreciated that I was mostly able to stick to just writing plain ol' vanilla HTML, CSS, and JS for the whole thing.

Next (and other meta-frameworks like Astro and Sveltekit) are great as BFFs.

Great work! Astro is such a breath of fresh air for sites that don’t need a heavy JS runtime.

I love it for SPA’s too! You can use anything you can use in an SPA that you can do with a normal app — just put it all in index.astro

Astro with Svelte is a good time.

I've been using Svelte since 2019 and so happy about it. One thing people don't understand when it comes to "ecosystem" is another one of those React-things. "Advantages" in a context where an advantage was never needed in the first place doesn't count. React might have a bigger ecosystem, but Svelte doesn't need it. This is because there's so little boilerplate for anything you need, it only takes a few minutes to essentially make your own.

sveltes magic is in the compiler. way less boilerplate, reactive by default. but smaller ecosystem means you might be building stuff from scratch more often.

I really don’t understand why you’d ever use React over Svelte on a new project.