Who is the team behind Astro? I forgot what they created before this.
Update, they created Snowpack (https://www.snowpack.dev), PikaCDN (now Skypack, https://www.pika.dev/cdn),
Astro 2.0
11–20 of 48 posts
Re: Astro 2.0
#12I read entire documentation yesterday, and I am very impressed. Looks fantastic, with some great conventions if you need it quick, but fully customizable if you change your mind later. I particularly like the fact that I can switch from SSG to SSR and back. File system as db, markdown with templating and js expressions, nasting layouts, quick random endpoints, filtering of collections, named slots everything repo fri…
Never heard of nanoc, interesting!
Re: Astro 2.0
#13How does Astro hybrid rendering compare to Qwik? https://qwik.builder.io/
Apparently Astro is faster.
https://docs.astro.build/en/concepts/mpa-vs-spa/#case-studie...
Re: Astro 2.0
#14How does Astro hybrid rendering compare to Qwik? https://qwik.builder.io/
To my understanding...
Astro is tries to rely on SSR as much as possible with MPA approach, so the client have to render as little JS as possible.
Qwiks goal is to be instant for every device, it does this by delaying the download & execution of JS so much it can. Qwik also partially renders the content in its state on the server, then sends it over to the client to do the rest.
Re: Astro 2.0
#15Once astro support in webstorm is complete it will be to me the perfect static site fx
Re: Astro 2.0
#16tried Astro recently and really, really love the DX and docs - so well executed
Re: Astro 2.0
#17Astro is nice but it misses the UX of instant page transitions via client side routing, so I switched back to NextJS.
Maybe I am not understanding completely what you are missing, but there is an SPA integration that gives you instant navigation. It also features pre-fetching, so it’s not limited to already visited pages.
Re: Astro 2.0
#18Who is the team behind Astro? I forgot what they created before this. Update, they created Snowpack ( https://www.snowpack.dev ), PikaCDN (now Skypack, https://www.pika.dev/cdn ),
I believe it was Snowpack.
Re: Astro 2.0
#19Astro is nice but it misses the UX of instant page transitions via client side routing, so I switched back to NextJS.
Maybe I am not understanding completely what you are missing, but there is an SPA integration that gives you instant navigation. It also features pre-fetching, so it’s not limited to already visited pages. https://github.com/RafidMuhymin/astro-spa
Then what's the point? With NextJS I can have SSR but with client side navigation hydration. It's simply a better solution for that use case than an almost year old random library for Astro. Astro is good for traditional MPAs that don't need much interaction.
Re: Astro 2.0
#20Had a hard time using MANY existing React ui components from various packages. I guess it is fast but the work involved in trying to build anything more interactive is not worth it just to shape 2-3-10ms. I can't find a plus for using this over something like Hugo (https://gohugo.io/) for example.