Content
@
0 reply
0 recast
0 reaction
Haole
@haole
https://www.datocms.com/blog/why-we-switched-to-astro Astro looks promising, but haven’t had the time to try it.
7 replies
5 recasts
32 reactions
Steve
@stevedylandev.eth
Definitely worth trying out! Imo one of my favorite subs for Next.js
1 reply
0 recast
3 reactions
Haole
@haole
Nice! Is there Next features you love but not in Astro?
1 reply
0 recast
1 reaction
Steve
@stevedylandev.eth
Honestly not really, the only thing you might miss out are libraries that only work in Next. Generally you can make due by using React components (it can mix React Svelte Vue and Solid; so dope) and scoping it down to what you need. It's a great framework for content heavy sites like a blog, but it also can do API routes, simple routing in general, static ssr or hybrid where you can do server islands, and a lot more.
3 replies
0 recast
1 reaction
artlu 🎩
@artlu
Migrated my personal website from Gatsby to Astro, loved it, 5-star experience. Made a few toy sites, loved the speed + flat learning curve. Mix+match frameworks is a joy; client-side state a mild challenge (no Redux, have to use nanostores). Built SassyHash user site on a very good Astro template. Had to work harder than expected to integrate Farcaster concepts. (HMU if you get stuck on SIWF/SIWN, it's doable and maybe 20% harder than using Remix?) Islands take some serious getting used to / re-arranging your mind. I find you have to think much harder about state than with a React site, but you get to schluff off many, many layers of extra JavaScript. Context providers is a no-go unless you go the "Austraila" route: one big island. Astro DB is a truly fascinating innovation, it boggles the mind how much compute it can avoid/save with minimal impact on DX or UX.
1 reply
0 recast
2 reactions
conca 🎩💻
@0xconca.eth
There are third party libraries for Next that don't work for plain React? 🤯
1 reply
0 recast
1 reaction
Haole
@haole
Thank you for this detailed explanation!
0 reply
0 recast
1 reaction
