I like Astro cause I’m a tinkerer. If I want to experiment with another framework I can. If I want to go full ssr I can. It’s almost a meta-meta framework in a sense cause they’ve tried for the most part to just do the heavy lifting when needed.
Not against next, im more exhausted in the dev influencer community. New doesn’t equate to now unfortunately the hype train has caused react fatigue.
I love it, I moved my personal website after trying it out a few weeks ago. It's my go-to for most websites now, and I use nextjs for the highly interactive "apps".
I like Astro a lot, but I still prefer Next. It took me a while to come around to it, but my experience with RSCs, server actions, and App Router has been really good lately. Also, partial prerendering is going to make using App Router even better.
With RSCs, it's making me appreciate component-oriented architecture so much more and React does this better than any other tool at the moment.
For straightforward static sites, Astro remains my go-to choice. I know it can do a lot more than that, but I prefer to use it solely for such purposes.
I dislike having to switch between astro components and other framework components. For the most part I use jsx frameworks, and it is pretty annoying that it is similar enough but with minor differences that annoy my workflow. I’d prefer a radically different syntax or preferably just jsx. Other than that me problem, top notch stuff.
Never be hard-core anything. Think critically for each project and pick whichever framework works best. Often that might be Next, sometimes it might be Astro.
I played with it a bit last year and loved it, would definitely use it again if I got the chance. It didn't seem well suited to projects that require authentication/user-specific sites, but that could be a skill/research issue on my end. Great for static sites and pure frontends though. Loved that I could combine Svelte and Markdown.
If you want to create a website that's SEO-friendly and performs well, you should check out Astro, but it's more than that. It's a really powerful tool that's easy to use. I'm not that guy who can compare and say which one is better between Next.js and Astro or whatever. Each tool has its own strengths and weaknesses, so you need to figure out which one is right for your specific needs. Astro is pretty cool because you can write code in React, Vue, Svelte, and some other stuff, but I haven't tried that yet. I think vanila Astro is the better pick for me, but you should make your own decision. peace.
Currently migrating the State of JS result app, what I lack in Astro:
- can't have middlewares for static content. If you need URL rewrites or similar, you need to use another solution like host provided equivalents (for instance use Vercel Edge middlewares, like you would do in a Next.js app). This makes i18n server redirection harder to setup, I am currently exploring this. I think using client-side redirections does the job if you want automated redirection via the "navigator.language" when the user doesn't ask for a specific locale explicitly via URL or cookies
- no incremental rendering, so no on-demand invalidation either. You render everything or go to per-request SSR + HTTP cache, there is no middleground yet (though it's discussed)
These are not blockers in many projects. The good part of Astro are:
- it's easy to mix different frontend stacks for interactive components if you need too
- the .astro syntax is cool, scoped style for instance is a blessing
- it has more built-ins for blogging
Basically if your site has a lot of hard-written markdown content to deliver (marketing site, blog etc.) Astro is excellent. If it's more an hybrid app with various requirements, Next.js is more flexible and feature-rich.
Hi OP, seems like you have got experience in next.js. I am stuck in very confusing bug. I desperately need your help as I couldn’t get any help in communities. Please dm me if you have 10 minutes.
I like Astro cause I’m a tinkerer. If I want to experiment with another framework I can. If I want to go full ssr I can. It’s almost a meta-meta framework in a sense cause they’ve tried for the most part to just do the heavy lifting when needed. Not against next, im more exhausted in the dev influencer community. New doesn’t equate to now unfortunately the hype train has caused react fatigue.
astro is moving fast and each feature is better than the previous! once react 19 comes out, we’ll be able to use RSCs over there pretty quickly.
Best developing experience recently. Astro has great docs and tutorials.
I love it, I moved my personal website after trying it out a few weeks ago. It's my go-to for most websites now, and I use nextjs for the highly interactive "apps".
Astro + SSR is as close to next (app router) you can get.
I like Astro a lot, but I still prefer Next. It took me a while to come around to it, but my experience with RSCs, server actions, and App Router has been really good lately. Also, partial prerendering is going to make using App Router even better. With RSCs, it's making me appreciate component-oriented architecture so much more and React does this better than any other tool at the moment. For straightforward static sites, Astro remains my go-to choice. I know it can do a lot more than that, but I prefer to use it solely for such purposes.
Yea I agree on the server components and the app router part
I just shipped a project using Astro. It’s pretty cool, but Next.js is just so much more flexible if you want to do any client-side routing.
I dislike having to switch between astro components and other framework components. For the most part I use jsx frameworks, and it is pretty annoying that it is similar enough but with minor differences that annoy my workflow. I’d prefer a radically different syntax or preferably just jsx. Other than that me problem, top notch stuff.
Never be hard-core anything. Think critically for each project and pick whichever framework works best. Often that might be Next, sometimes it might be Astro.
Next is better for applications. Astro is better for content heavy websites. Both are great tools.
I played with it a bit last year and loved it, would definitely use it again if I got the chance. It didn't seem well suited to projects that require authentication/user-specific sites, but that could be a skill/research issue on my end. Great for static sites and pure frontends though. Loved that I could combine Svelte and Markdown.
If you want to create a website that's SEO-friendly and performs well, you should check out Astro, but it's more than that. It's a really powerful tool that's easy to use. I'm not that guy who can compare and say which one is better between Next.js and Astro or whatever. Each tool has its own strengths and weaknesses, so you need to figure out which one is right for your specific needs. Astro is pretty cool because you can write code in React, Vue, Svelte, and some other stuff, but I haven't tried that yet. I think vanila Astro is the better pick for me, but you should make your own decision. peace.
Astro is my no brainer go to if I need an SSG based site.
lol i just 2 ago reading their docs
for SSG its better choice
Currently migrating the State of JS result app, what I lack in Astro: - can't have middlewares for static content. If you need URL rewrites or similar, you need to use another solution like host provided equivalents (for instance use Vercel Edge middlewares, like you would do in a Next.js app). This makes i18n server redirection harder to setup, I am currently exploring this. I think using client-side redirections does the job if you want automated redirection via the "navigator.language" when the user doesn't ask for a specific locale explicitly via URL or cookies - no incremental rendering, so no on-demand invalidation either. You render everything or go to per-request SSR + HTTP cache, there is no middleground yet (though it's discussed) These are not blockers in many projects. The good part of Astro are: - it's easy to mix different frontend stacks for interactive components if you need too - the .astro syntax is cool, scoped style for instance is a blessing - it has more built-ins for blogging Basically if your site has a lot of hard-written markdown content to deliver (marketing site, blog etc.) Astro is excellent. If it's more an hybrid app with various requirements, Next.js is more flexible and feature-rich.
Hi OP, seems like you have got experience in next.js. I am stuck in very confusing bug. I desperately need your help as I couldn’t get any help in communities. Please dm me if you have 10 minutes.
Please don’t ask for unsolicited help
https://www.reddit.com/r/nextjs/s/ppNDiFdJAl Please help