Side by side
Astro vs Vue.js
Astro
17 positive (100%) · 0 mixed (0%) · 0 negative (0%)
Trust + time weighted: +100%
Top excerpts
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
Vue.js
10 positive (63%) · 5 mixed (31%) · 1 negative (6%)
Trust + time weighted: +58%
Top excerpts
Previous clients were happy with small Angular/Vue apps, and I enjoyed the great DX from tools like Vite, Docker, and Swagger APIs
So no React, jQuery, Vue, whatever, but actually build an understanding for what's happening and then you can dive deeper as you want.
I had workeräd.with both angular and Vue before this - and many other utility frameworks.
HTMX is good when you *don't actually need* a full-blown SPA. It's not just for "simple projects", it is built around a different philosophy than things like React/Vue/Svelte.
the main tradeoff is you can't do the ultra-smooth offline-first stuff that react/vue excel at.