Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Astro 2.0

astro.build

Post reply on HN
Print view View original

21–30 of 48 posts

Re: Astro 2.0

#21

Post by lern_too_spel »

Alifatisk wrote: post #14
lern_too_spel wrote: post #8

How 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.

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.

Re: Astro 2.0

#22

Post by verzeichnis »

satvikpendem wrote: post #19
verzeichnis wrote: post #17

Earlier quoted context omitted.

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.

Sure, I wasn’t saying Astro is for every use case. Like, no tool ever is.

Re: Astro 2.0

#23

Post by satvikpendem »

verzeichnis wrote: post #22
satvikpendem wrote: post #19

Earlier quoted context omitted.

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.

Sure, I wasn’t saying Astro is for every use case. Like, no tool ever is.

Indeed, hence why I said I moved back to NextJS for my use case, personally speaking.

Re: Astro 2.0

#24

Post by __Parfait__ »

helij wrote: post #4

I like the idea of "performant, content-focused websites" but the website itself hosting Astro doesn't really feel performant. When I scroll down it struggles on my quite powerful desktop computer.

The homepage is text and static images.. I doubt the issue is with them

Re: Astro 2.0

#25

Post by POiNTx »

Does anyone have any experience with Astro and Sveltekit? What would you choose over the other one in which situation? Is Astro only used for websites that just display content, while Sveltekit can be used for more complex webapps?

Re: Astro 2.0

#27

Post by fks »

acedTrex wrote: post #15

Once astro support in webstorm is complete it will be to me the perfect static site fx

https://youtrack.jetbrains.com/issue/WEB-52015/Astro-Languag...

> Hi everyone! Sorry for not posting the announcement here, too. I can confirm that we’re going to add Astro support in v2023.1. We will keep you posted on our progress once we start working on the issue and will ask you to give Astro support a try and share your feedback with us. Please keep monitoring the issue for updates.

Sounds like it's coming soon!

Re: Astro 2.0

#28

Post by axwdev »

POiNTx wrote: post #25

Does anyone have any experience with Astro and Sveltekit? What would you choose over the other one in which situation? Is Astro only used for websites that just display content, while Sveltekit can be used for more complex webapps?

I’ve been evaluating these two along with some other options for a project over the last couple of weeks.

If you have pretty much entirely static content, Astro will almost definitely be more suitable due to the lower JS you’ll be shipping.

If you need complex interactions and nice client side routing you’ll want SvelteKit. You can embed SPA routers etc within Astro but I feel like once you’re going down that route you might as well just use a more appropriate meta framework.

For something in between, it’s a toss up.

I will say SvelteKit is the best frontend meta framework I’ve tried so far. Happy to answer any specific questions.

Re: Astro 2.0

#30

Post by mikojan »

chimen wrote: post #20

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.

Every time I returned to my Hugo project it felt like I had to learn everything all over again.

With Astro it is just components. I am used to those. The cognitive load is much lower.

Post reply on HN