41–48 of 48 posts
I recently tried to get MDX to work with Next.js app directory. It might be possible, bit I did not have the patience. Astro might just be the solution. It is for a largely text-based project.
How 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...
They're going out of their way to imitate the lazy-loading Qwik does by default for the parts that require heavy-lifting, once they disable that the magic's gone.
They weren't, as expert frontend programmers, even 100% sure about what was causing the high scores at first and they had to go and check if it was the lazy-loading for themselves. I'd give an average dev something with the Qwik approach, where they don't have to choose and automated analytics-based PGOs can be performed.
With that said they stated that the server-side rendering part of Qwik is not very optimized. I'd love to see if Qwik.js can get their SSR to perform better or if someone else (hopefully in a better language and runtime) is able to knock that one out of the park.
Earlier quoted context omitted.
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.
Qwik can fully render server-side, but if you cause an update, it downloads the minimum JS needed to make that update on the client.
I 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!
The project is also 15+ years old and continiously developed.
We switched to Astro a few months ago. Some team members were not super convinced since NextJs is better known but during our spike to test them both out Astro came on top on ease of use. We have now been in production for a couple of months and could not be happier. It’s very straight forward for simple sites but we switched a couple of legacy react apps to SSR with it and it was super easy and developer experience…
Was this post written by ChatGPT? Were many other comments in this thread written by people with undisclosed interest in this project (e.g. employees, founder friends)? Maybe I'm thinking too much about it, but I got triggered by "This new release is a game-changer for anyone working with Markdown on the web", the style of writing is very similar to ChatGPT... Also, I work with markdown on the web and never had any p…
For content based sites it definitely feels like a massive game-changer because you can write everything in any framework and render it all to static HTML. Or if you need some JS you get hydrations out of the box for free.
The type-safe MD/MDX in 2.0 seems very useful as well. Pre-defined functions for fetching content which have auto-completion and typing sounds very exciting for DX.
Had 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.
This video release late but might be useful for introduction to Astro.