Hacker News Reader

Comment by tancop | Hacker News Reader

Astro comes out on top with the best time, #2 lowest spend and zero client side JS. I know what I'm using for my next project.

View on HN

It scores well here because Astro is for “content-driven websites” and that’s what the benchmark app was. I’d be curious how different the results would be if the app was highly interactive, with nontrivial realtime/async stuff going on etc.

And then you just use your favorite js framework with Astro and it will still be good. I use Astro with react and heroui a lot. Since the latter does not need any js for many components anymore you still get zero js builds unless you actually need interactivity.

I actually find that agents are not especially performant with the “use Astro plus whatever” approach.

They seem to struggle to reason about the boundary between the two.

I haven't found that. I use Astro + SolidJS and it seems to work very well.

I intentionally avoid hydration (which I've always found to be flaky) and hydration-based frameworks like SolidStart, so possibly that helps. Or maybe that's just my own bias!

Agreed. Go with solidstart (who just released a big V2 upgrade a few months back) if you want an extremely elegant solution to async, error handling and heavily concurrent behaviors.

Very easy to setup and way more readable than the equivalent React code.

Even for highly interactive projects, Astro is still my favorite build system. Just toss the SPA component into the single Astro file and you're done.

Can confirm Astro is very very pleasant to use, and the escape hatches for when you do need something a bit more heavy hitting feel very well designed.

> I know what I'm using for my next project.

Django?

But is zero client side JS necessarily better? I prefer the progressive enhancement philosophy of SvelteKit. When your internet connection and browser does support JS, it makes for a faster user experience.

next project? pun of the year?

Reply on news.ycombinator.com