The marketing seems better than the product. With the tutorial it's a lot of setup and you eventually get to the component page where it doesn't really say how it works. <a href="https://docs.astro.build/en/tutorial/3-components/2/" rel="nofollow noreferrer">https://docs.astro.build/en/tutorial/3-components/2/</a><p>I feel like it's more clear what's going on under the hood with SvelteKit, Nuxt, Next.js, Remix, Solid Start, and other ones I've looked at. However I was starting to get a little familiar with Astro, and already a new major version. It feels rushed.<p>I'll see what happens with Astro 3, I'm not saying I don't like it, just that the marketing is more impressive to me than what I've seen in the tutorials I've tried following thus far.<p>Also I think it might be time to make it so repos can link to syntax highlighting and be highlighted with them using tools such as GitHub and vscode until you specify one manually. That way new syntaxes can be supported more rapidly. They could be run with WebAssembly to sandbox them.
First time I'm hearing about the View Transitions API<p><a href="https://developer.mozilla.org/en-US/docs/Web/API/View_Transitions_API" rel="nofollow noreferrer">https://developer.mozilla.org/en-US/docs/Web/API/View_Transi...</a>
I don't know exactly who is the "first" but Svelte just announced this a few days ago:<p><a href="https://svelte.dev/blog/view-transitions" rel="nofollow noreferrer">https://svelte.dev/blog/view-transitions</a>
Major discussion 23 days ago:<p><a href="https://news.ycombinator.com/item?id=37108111">https://news.ycombinator.com/item?id=37108111</a><p>(167 points/129 comments)
<i>> Unlike many frameworks, Astro uses standard HTML <a> elements to navigate between pages (also called routes), with traditional page refreshes.</i><p>I love it. Truly amazing that this is the exception these days.