Side by side
Astro vs Laravel
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
Laravel
10 positive (53%) · 7 mixed (37%) · 2 negative (11%)
Trust + time weighted: +39%
Top excerpts
I noticed this weird 8194460 text that was appearing on my laravel website and causing the layout to break.
It also ships with Laravel (many install paths) - this bumps its numbers quite a bit
Laravel with React
It’s good to learn to do that for sure and I admire your spirit but also seriously learn about frameworks. Look at Laravel or Symfony for example.
My little Laravel adventure gave me a good introduction to the MVC pattern, which still feels overcomplicated but I trust that the benefits will probably appear when projects get bigger.