Live data from Hacker News

Cloudflare acquires Astro

astro.build

111–120 of 409 posts

Re: Cloudflare acquires Astro

#115
post #63

Earlier quoted context omitted.

> CloudFlare is hardly "big tech" yeah, it's still losing money

[flagged]

> according to Gemini

thanks for the unrequested slop!

you know what GAAP stands for?

"generally accepted accounting practices"

so what does non-gaap mean?

"non-generally accepted accounting practices"

aka: bullshit

Re: Cloudflare acquires Astro

#116
My favorite framework, and what has brought me much deeper into the world of web development. It's what I have used for me personal page https://bryanhogan.com/ . I'm happy to see it get funding, although I hope this doesn't introduce entshittification. So far I'm hopeful though.

It's the first framework I recommend to web dev beginners, after they have built something with plain HTML and CSS.

Re: Cloudflare acquires Astro

#117
post #80

Earlier quoted context omitted.

Netlify didn't buy Gatsby for the framework. They wanted the hosting business and the GraphQL thing. They said this at the time, and it's true. It was barely resourced. Cloudflare is only interested in the framework (because Astro has nothing else). Source/disclosure: I worked at Gatsby, Netlify, Astro and Cloudflare

Why did they want Gatsby's graphQL thing? What was attractive about it?

Seemed a good idea at the time. The unified data layer was always the best thing about Gatsby (which is why I nicked the idea for the Astro content layer), but maybe not as a hosted product

Re: Cloudflare acquires Astro

#118

Earlier quoted context omitted.

Yeah, I'm not sure I understand why "islands" isn't just "bits of JavaScript on a static page". It feels like the "JavaScript as a Server Side Language" folk are just repeatedly re-inventing stuff that has been done a million times by other systems with a different back-end only with a new fancy name.

It has been funny seeing the tide come in and out now a few times. Though I will admit that each time, the ergonomics get better. AJAX as a pattern was pretty gnarly if you wanted to do a bit more than update a notification badge or comment box. There's a really nice pattern of using Custom Elements [0] for that sort of JS interactivity sprinkling. You can make your web application however you want, and when you want…

Custom Elements do start to feel like the dream of the Knockout-era web of "Progressive Enhancement" is finally almost entirely out of the box in the browser. Especially ignoring the Shadow DOM and using Light DOM to style your unpopulated or static rendered fallback states as close to your "live" JS-driven state can lead to some very good experiences, including and especially when JS is disabled (or erroring).

Re: Cloudflare acquires Astro

#119
post #35

I like the idea behind Astro, I've used it for a couple websites here and there. I'm a bit worried about the complexity brought by Astro supporting all these different frameworks through its adapters, and how stable and maintainable those websites will be in the future. For instance: I've been using Astro with Svelte to build static sites with some components that require client-side interactivity. I really like that…

Any reason you didn't use alpine for client side interactivity? When I went down the "use a framework plugin in Astro" route, I found it too jarring and reverted to alpine which I found worked well enough.

No, not in particular, I just like Svelte's compilation-based approach, but Alpine definitely looks nice.

When the client side interactivity is very contained and small in scope I also quite like just using plain JavaScript without a framework.

Post reply on HN