> Now Astro is downloaded almost 1,000,000 times per week [...]
Are these numbers supposed to provide any sense of the popularity if you're not often looking at npm trends?
Cloudflare acquires Astro
221–230 of 409 posts
Re: Cloudflare acquires Astro
#222I don’t want a framework that’s coupled to a hosting provider.
It's not and will probably never be. If you want some precedent look at Hono. Initially it was just for the CF Workers runtime (not developed by CF). Then CF started using Hono internally and hired the dev to work on Hono full time. Hono works on any JS runtime. https://hono.dev/docs/concepts/web-standard
I suppose we’ll see — I’d be surprised if the whole promise of nothing will change don’t hold over the long term. I don’t love that Astro is tied to a narrow set of hosting providers either.
Re: Cloudflare acquires Astro
#223Re: Cloudflare acquires Astro
#224Earlier quoted context omitted.
This is insane to me, and validates my irrational dislike of next.
Definitely irrational. There are lots of logical reasons to dislike Next (like the fact that they pile new shiny bit on top of new shiny bit without caring about the regular user experience) ... but being mad that it can't run on Vite is silly. It's like being mad that Rails can't run on Python, or that React can't run on jQuery. Next already has its own build system, so of course it doesn't work with another build s…
Isn’t the next.js build system known for being slow/memory hungry?
Re: Cloudflare acquires Astro
#225Earlier quoted context omitted.
So, cloudification: lock the customer into a complex cloud dependent solution they can't easily migrate to some other commodity infrastructure provider.
What lock in? They explicitly said: > Staying open to all was a non-negotiable requirement for both us and for Cloudflare. They have deployment guides for practically every provider out there: https://docs.astro.build/en/guides/deploy/ And at the end of the day, most of the deployment is just deploying a static site... Which you can do practically anywhere.
Yeah. For now.
Re: Cloudflare acquires Astro
#226Earlier quoted context omitted.
So, cloudification: lock the customer into a complex cloud dependent solution they can't easily migrate to some other commodity infrastructure provider.
No? It's still the same Astro that you can move to any other provider that supports it - and it's just Javascript, so pretty much everyone supports it.
For now.
Re: Cloudflare acquires Astro
#227Great 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.
How to measure the popularity of FOSS projects though?
Number of downloads? Number of stars on GH? Number of content on social medias?
The absolute value is meaningless in itself, but there's a big difference between a library that is downloaded a thousand or millions of times each week. That's the idea.
Meanwhile for-profit projects have actual customers or revenues to demonstrate popularity.
Re: Cloudflare acquires Astro
#228Is that a good deal for the employees of Astro? They're now Cloudflare employees, which I guess looks good on your CV.
But do such acquihires usually result in higher salaries for regular (non-leadership) employees or? Also, what about NSOs?
Re: Cloudflare acquires Astro
#229I have always liked Astro. It also works great with AI tools since its combination of markdown and code. Was able to vibe code a quick blog template and deploy to cloudflare in minutes with an existing headless backend - https://sleekcms-astro-blog.pages.dev/
Re: Cloudflare acquires Astro
#230Earlier quoted context omitted.
What lock in? They explicitly said: > Staying open to all was a non-negotiable requirement for both us and for Cloudflare. They have deployment guides for practically every provider out there: https://docs.astro.build/en/guides/deploy/ And at the end of the day, most of the deployment is just deploying a static site... Which you can do practically anywhere.
Yeah. For now.
That's always been true. Perhaps even more so as Astro constantly faced an existential battle for a working business. Now they don't have to do that and Cloudflare makes their money on their infra business. Locking Astro up now or in the future gains them very little compared to how much they make with hosted upsell services. [edit: clarity]