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

Cloudflare acquires Astro

astro.build

Post reply on HN
Print view View original

361–370 of 409 posts

Re: Cloudflare acquires Astro

#361

Post by willtemperley »

mmooss wrote: post #341

I don't understand how Cloudflare's bottom line benefits: Some here say they gain Astro users, that Cloudflare will become part of the default deployment. But given Cloudflare's current scale, how much are Astro's users worth? Is it even worth the distraction for Cloudflare? Companies lose energy to lots of small, low-value operations. Most acquisitions begin with announcments that nothing will change, in order to re…

They get control and market differentiation. There will probably be a CloudFlare Astro CMS offering.

I personally would like a highly managed Astro solution. Astro is simple but highly extendable.

I can only hope they wean themselves off NPM somehow.

Re: Cloudflare acquires Astro

#363

Post by catlifeonmars »

JavierFlores09 wrote: post #338
css_apologist wrote: post #238

Earlier quoted context omitted.

i'm interpreting this in the reverse if dev tools can only be "monetized" by being bought out, it does not feel sustainable on any level we will see companies attempt to do things like close source these projects, go subscription based, or just straight up drop support there is no incentives for cloudflare to make astro better, or even keep it around same goes with bun, svelte, and i'm sure countless others

Who's to say there's no incentive. Anthropic using Bun internally is plenty incentive to make it better even if for their own use-case. I think it is a bit of a doomer perspective to think anything being bought out means the end of the line for that project. Sure, some things might change depending on the interests of the new owners but that's not to say it'll automatically become bad. Microsoft bought Github and Moj…

GitHub continues to become less and less usable (slower performance) while the number of features proliferate. On the one hand, being part of larger company _can_ relieve the pressure to stay profitable. But on the other hand, acquisitions tend to get cannibalized by the companies that acquire them. Profitability tends to become less and less aligned with usability.

Re: Cloudflare acquires Astro

#365

Post by alexjurkiewicz »

mmooss wrote: post #341

I don't understand how Cloudflare's bottom line benefits: Some here say they gain Astro users, that Cloudflare will become part of the default deployment. But given Cloudflare's current scale, how much are Astro's users worth? Is it even worth the distraction for Cloudflare? Companies lose energy to lots of small, low-value operations. Most acquisitions begin with announcments that nothing will change, in order to re…

Developer goodwill. And it probably cost a song.

Re: Cloudflare acquires Astro

#366

Post by pjmlp »

azangru wrote: post #333
pjmlp wrote: post #306

Earlier quoted context omitted.

Or I don't know, use WebComponents.

How would this help? You would want your header render on the server, wouldn't you? Not to incur a CLS penalty, right? How does a web component help in this scenario?

You use server includes in that case, a simple Apache configuration.

Welcome to the 1990's web coding.

Re: Cloudflare acquires Astro

#367

Post by some1else »

mmooss wrote: post #341

I don't understand how Cloudflare's bottom line benefits: Some here say they gain Astro users, that Cloudflare will become part of the default deployment. But given Cloudflare's current scale, how much are Astro's users worth? Is it even worth the distraction for Cloudflare? Companies lose energy to lots of small, low-value operations. Most acquisitions begin with announcments that nothing will change, in order to re…

Why does Vercel provide Next.js? Aside from talent & tightly coupling Astro to their services, their North Star might be similar to Weekly Number of New Domains Hosted On Cloudflare. Sponsoring a framework that helps ship performant websites feeds into that metric.

I have no inside knowledge, though.

Re: Cloudflare acquires Astro

#369

Post by Joeri »

css_apologist wrote: post #238
arjie wrote: post #166

Very nice to see these dev tools get an exit. e.g. I love `uv` and friends but did consider that perhaps dev tools are just a bad business and then no one will go into making that kind of stuff. Good exits means more of these tools. I have only used Astro for toy stuff but it seemed neat. Congrats to the team. EDIT: To put paid to the sidebar discussion below, yes I meant "for instance, consider `uv`; they might do t…

i'm interpreting this in the reverse if dev tools can only be "monetized" by being bought out, it does not feel sustainable on any level we will see companies attempt to do things like close source these projects, go subscription based, or just straight up drop support there is no incentives for cloudflare to make astro better, or even keep it around same goes with bun, svelte, and i'm sure countless others

Realistically to maintain a modern web framework to even a minimal standard you need a few people working fulltime on it, and more than a few if you want to take it places. There needs to be some kind of long term sustainable vehicle for funding those developers, either a corporate sponsor or a foundation.

So all those frameworks have to end up somewhere, and I’d rather it be somewhere else than vercel, as they already own way too much of the web frontend space.

Re: Cloudflare acquires Astro

#370

Post by scoot »

rdiddly wrote: post #343
woodruffw wrote: post #207

Earlier quoted context omitted.

I don't think that's really clear. I think we could both defer to the OP clarifying. For pedantry's sake: neither i.e. nor e.g. would be correct here. You want cf. ("conferatur") to invite a comparison; e.g. is when an example pertains to an instance . In this case uv would not pertain to the instance, because Astro is not Astral.

"e.g." IS correct because uv is an example or instance of a dev tool.

"e.g." isn't used correctly here. It's intended use is as a connector linking a clause to examples supporting that clause. You can't simply substitute "for example" with "e.g." anywhere in a sentence and expect it to function correctly.

Regardless, these Latin abbreviations best avoided entirely due to the surprising number of readers who don't understand them.

Post reply on HN