Live data from Hacker News

Astro 2.0

astro.build

31–40 of 48 posts

Re: Astro 2.0

#31

Astro is nice but it misses the UX of instant page transitions via client side routing, so I switched back to NextJS.

You mean it misses the UX of instantly interrupting you with random flashes of spinners and skeleton elements.

Re: Astro 2.0

#32
post #31

Astro is nice but it misses the UX of instant page transitions via client side routing, so I switched back to NextJS.

You mean it misses the UX of instantly interrupting you with random flashes of spinners and skeleton elements.

No, I don't mean that, actually.

Re: Astro 2.0

#33
Been building my blog with this the last couple of weeks. It's great and this version seems to sand down some of the rough edges (error messages used to be terrible, now they look like they'll be useful, content collections mean I don't have to glob everything then filter). Oh and markdown type checking is really cool. Looking forward to seeing how it develops over the next few years.

Re: Astro 2.0

#34
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 problems with it, not sure what's the problem solved by Astro.

Re: Astro 2.0

#35
post #34

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…

The previous sentence before your quote:

> Astro now helps you organize your Markdown with built-in parsing, validation, and automatic TypeScript type generation.

The bolded text leading the paragraph of your quote:

> deliver complete type-safety for Markdown and MDX

The announcement is about typing MDX. Also, Astro just works out-of-the-box with MDX, Next.js you have to do configuring. In others your don't get SSR. Personally Astro has the easiest and most flexible markdown experience ever. It makes sense to focus on that support and to lead with it. You can even have templates in JSX with MDX content files, cool stuff like that.

The Hybrid Rendering feature is really cool too. I have a few pages I wanted to SSR, but most of the site can be SSG. This saves from needing two projects. I can select pages to generate at build.

The rest of the error message optimization and dev tool improvements is always welcome.

Not affiliate with Astro btw.

Re: Astro 2.0

#37
I think I will give Astro another try but from my experience it was a bit clunky. There were a ton of dependencies and it did not go smooth at the beginning.

Re: Astro 2.0

#38
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.

Re: Astro 2.0

#39
post #9

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…

Did you start by rendering all of the react app as a fat island?

Re: Astro 2.0

#40
post #9

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…

Did you start by rendering all of the react app as a fat island?

Yeah we moved in 3 react apps in to the repo and each one is an island essentially
Post reply on HN