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

Astro is a return to the fundamentals of the web

websmith.studio

Post reply on HN
Print view View original

81–90 of 268 posts

Re: Astro is a return to the fundamentals of the web

#81

Post by niam »

ttoinou wrote: post #23

I spent a small amount of time looking into Astro and I didn’t get the difference with the Fresh framework created by the Deno team.. ? Fresh does this Island architecture already, and benchmarks on Astro website dont include Deno+Fresh to compare. So I’m still wondering what’s the benefit of using Deno+Astro vs. Deno+Fresh

Astro and Fresh were both inspired by the islands idea which was iirc coined by an Etsy frontend architect and further elaborated on by the creator of Preact.

My understanding is that Astro is able to more-or-less take a component from any combo of popular frameworks and render it, whereas Fresh is currently limited to just Preact via Deno. I think the limitation is to optimize for not needing a build step, and not having to tweak the frameworks themselves like Astro does (did?).

I'm not affiliated; I've just looked at both tools before.

Re: Astro is a return to the fundamentals of the web

#83

Post by owebmaster »

esseph wrote: post #39
falcor84 wrote: post #32

Earlier quoted context omitted.

I don't think it should suck at all. As I see it, RLHF empirically validated that this is the writing style people find to be the best.

Maybe you've never been told you sound like a robot, then. Feeling less-than-human isn't great.

Are you the post author?

Re: Astro is a return to the fundamentals of the web

#84

Post by 0x445442 »

archerx wrote: post #35
diggan wrote: post #10

> Traditional frameworks hydrate entire pages with JavaScript. Even if you've got a simple blog post with one interactive widget, the whole page gets the JavaScript treatment. Astro flips this on its head. Your pages are static HTML by default, and only the bits that need interactivity become JavaScript "islands." Back in my days we called this "progressive enhancements" (or even just "web pages"), and was basically…

I remember when it was called AJAX. We have completely lost the plot.

It's why Alan Kay calls our industry a Cargo Cult and says it's much more akin to the fashion industry than engineering.

Re: Astro is a return to the fundamentals of the web

#86

Post by pheew »

steve_taylor wrote: post #38
teekoiv wrote: post #20

It's baffling to me why more SSR frameworks, Astro and NextJS namely, can't adopt static pages with dynamic paths like SvelteKit. So for example, if you have a page /todos/[todoId] you can't serve those in your static bundle and NextJS straight-out refuse building your app statically. Whereas with SvelteKit, it builds happily and does this beautiful catch-all mechanism where a default response page, say 404.html in C…

You can indeed do that with Next.js. In the app router, it’s called generateStaticParams. In the pages router, it’s getStaticProps.

This isn't the same as getStaticProps is evaluated at build time not runtime

Re: Astro is a return to the fundamentals of the web

#88

Post by rob »

pentagrama wrote: post #67

But it has a CMS? The author said that replaced WordPress sites with Astro, and on https://astro.build/ I see a comparison to WordPress. Astro brings a friendly UI to maintain and update the sites? Like the WordPress panel and editor.

It doesn't, which is why all these solutions breakdown long-term compared to things like WP for small biz brochure stuff. 5 to 10 years from now when you're no longer talking to your client who has absolutely no technical experience, they're not gonna know that their website code is in some random GitHub repository that needs to be compiled with vite and then you need to magically wait for Netlify/etc to pull in your changes. They'll probably be fuming they have to find a developer that knows how to edit and manage that compared to something like WordPress which is used for the majority of those websites.

Re: Astro is a return to the fundamentals of the web

#89

Post by fkyoureadthedoc »

ansc wrote: post #57
falcor84 wrote: post #27

Earlier quoted context omitted.

What does this have to do with LLMs? Are you just uncomfortable with dashes?

You're not just venting about me being uncomfortable with dashes — you are making a philosophical claim about what comfortability really means. And that? That is a true super-power.

The quote you posted from the article isn't even the right size of dash though. It's a hyphen, not an em dash. And an LLM would have it properly touching the surrounding text.

Re: Astro is a return to the fundamentals of the web

#90

Post by mbirth »

thibaultamartin wrote: post #25
diggan wrote: post #17

Earlier quoted context omitted.

> - It's still html and css centric - Once built, it doesn't require js by default - You can still opt-into adding js for interactivity here and there I've never used Astro so forgive my ignorance, but isn't that just creating a .html file, a .css file and then optionally provide a .js file? What does Astro give you in this case? You'd get the same experience with a directory of files + Notepad basically. It's also e…

Fair questions. For the first one, the main benefits of Astro over static html and css (for my use cases) are the ability to include components and enforce the properties that must be passed. A typical example would be [here][0] where I define a layout for the whole website, and then [on each page that uses it]( https://github.com/matrix-org/matrix-conf-website/blob/main/... ) I have to pass the right properties. Doa…

Embedded CSS circumvents proper caching of the CSS. Also, with HTTP/2 your client can download several resources in one transaction. So, it shouldn’t make much of a difference with CSS embedded or separate. Just, that embedded CSS has to be loaded over and over again whereas a separate file can be cached and reused from the local cache.
Post reply on HN