Live data from Hacker News

Cloudflare acquires Astro

astro.build

211–220 of 409 posts

Re: Cloudflare acquires Astro

#212

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.

cf. would invite a fair bit of confusion on an article about cloudflare

I agree! That's why I think it's probably just a confusion between entities. It doesn't make sense either as example or as a comparison (although IMO it makes more sense as the latter).

(For the OP: I'm sorry if I misinterpreted you.)

Re: Cloudflare acquires Astro

#213

Earlier quoted context omitted.

This is Astro, not Astral. uv is Astral :-) Edit: OP clarified what they meant, I'm sorry for the misunderstanding on my part!

They know, hence why they used e.g., i.e. exempli gratia

For the perplex:

e.g. is latin for "exempli gratia" = for example i.e. is latin for "id est" = that is

Re: Cloudflare acquires Astro

#214
Great for Astro..

About the download stats for open source frameworks and libraries.. I keep reading claims of "millions of weekly downloads" -- surely this is a noisy metric, right?

NPM just counts GET requests. A significant number of those must be from CI/CD pipelines, mirrors, build servers, etc.

It still signals popularity, but probably to a much lesser degree than implied.

Re: Cloudflare acquires Astro

#216
post #187

Earlier quoted context omitted.

I use Astro so I could make my blog a static site and deploy it to Cloudflare pages. I was impressed since I got interactive compilation and state tracking of how many exercises the user completed. https://jjmarr.com/blog/structured-bindings-structs/

I have a question. Why can't Whatsapp or Meta make a markdown INFO only website for small business owners (e.g. technicians, shopkeepers, handyman, etc) using their immense reach and clout. The method of using whatsapp groups to keep users updated of the latest updates is not scalable or open.

too big to deliver simple solutions? youre making way too much sense and this would die in committee or be replaced when someone new needs to justify themselves by launching a new product to supplant an existing one.

Re: Cloudflare acquires Astro

#217
post #99

Earlier quoted context omitted.

HTML. Unironically have been migrating my static pages (from Nextjs and Eleventy) to plain HTML and love it. Of course depends on your use case if that is feasible.

Plain html has two things going against it. First, it doesn't have any provisions for code reuse. So, if you have multiple pages that use the same header, same footer, or same navigation menu, your options are either to copy-paste it (gross), or to build the final html out of smaller pieces, at which point you've reinvented either a static site generator or a web server. Second, if you write long stretches of text, t…

> at which point you've reinvented either a static site generator ...

It doesn't have to be Astro though. You can build something super simple that just includes the header, footer, and nav. Leaving most of the site as plain HTML.

Re: Cloudflare acquires Astro

#218
post #22

It would be good to understand what Cloudflare gets out of the deal. The article is very much just "Astro, but someone else pays the bills!" which is of course lovely for Astro.

Same reason vercel buys open source... it makes cloudflare always a great deployment option for all Astro sites, which in turn helps cloudflare's core business. For example, Cloudflare released their vite plugin which makes it effortless for frameworks that use the vite env API to run inside workerd (meaning you get to use cloudflare service bindings in dev) back in April and only React Router had support for it. Nex…

So when folks say they want to see big companies invest in open source, this is what that looks like. CF could have kept coasting on what Astro was building, but instead they are paying for it. But in return they get a lot of control.

Re: Cloudflare acquires Astro

#219
post #39

> In 2021, Astro was born out of frustration. The trend at the time was that every website should be architected as an application, and then shipped to the user’s browser to render. Was it? Hot damn, I knew it'll eventually happen, but we truly are just running around in circles. Eventually these same people will do the same loop around, creating new frameworks because the current "server client" model suddenly doesn…

IMO it's because the web has a huge diversity of behaviors (in a way that, say, native apps do not) but a monoculture on the development side. React makes sense if you're making Gmail. It doesn't really make sense if you're making a mostly static blog. But because there are more job opportunities in the former (when you consider the wealth of internal web apps out there in the world) all the training courses folks ta…

Many technical directions in the past 15 years have been a thinly veiled attempt to actually get paid for doing work.

Re: Cloudflare acquires Astro

#220

Earlier quoted context omitted.

This is Astro, not Astral. uv is Astral :-) Edit: OP clarified what they meant, I'm sorry for the misunderstanding on my part!

They know, hence why they used e.g., i.e. exempli gratia

I'm not sure. I wouldn't generally call Astro a "dev tool". It's more of a framework.

It's possible you are right, but it isn't clear from the content of the comment.

Post reply on HN