Oh wow, Cloudflare enschitification is practically in real time right now.
Cloudflare acquires Astro
261–270 of 409 posts
Re: Cloudflare acquires Astro
#262Why does Cloudflare need a web framework? Most obvious would be they think they can make money from hosting astro sites (like Vercel and NextJS). I hope Cloudflare's impact on Astro will be tiny. But another great thing being swallowed by big tech...
This is overly cynical without reason. CloudFlare is hardly "big tech" even if it is a "big" "tech" company. They have no record of killing or abusing open source projects.
Maybe not by market capitalization but Cloudflare is used by around 25 % of the web. Internet giant in my books.
Re: Cloudflare acquires Astro
#263Very 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 think DevTools can be a very good money maker… I wrote two apps that were basically dev tools and they were the biggest of my money makers. I think it’s easier to make money from dev tools that are “apps” than dev tools that are “fundamental technologies” though so it probably heavily depends on the type of dev tools…
Re: Cloudflare acquires Astro
#264Why does Cloudflare need a web framework? Most obvious would be they think they can make money from hosting astro sites (like Vercel and NextJS). I hope Cloudflare's impact on Astro will be tiny. But another great thing being swallowed by big tech...
> But another great thing being swallowed by big tech... I will never use Cloudflare if I can help it, but this outcome is preferable to Astro becoming abandonware.
There are so many more options than being acquired and abandonware. Its hard but there are many independent and stable open source projects.
Re: Cloudflare acquires Astro
#265I’ve used Astro on Cloudflare for a few years for my personal website (username.com). They’ve both been absolutely fantastic, I can’t say enough good things about both of them. My website has all 100s on PageSpeed/Lighthouse, and that’s because of the performance focus of both Astro and Cloudflare. No credit to me at all. It was mainly because Astro prioritised shipping 0 JS unless it was absolutely necessary and Clo…
amazing performance.
Re: Cloudflare acquires Astro
#266All wrongs in Gatsby have been gotten right in Astro. What will happen next remains to be seen, but currently Astro is amazing for a few specific cases it covers. The performance, developer experience and documentation are all great.
Re: Cloudflare acquires Astro
#267Earlier quoted context omitted.
the naming is backwards then. An island is static, an ocean is not. See how it is a buzzword up to your interpretation?
now that you say it :o Should be astro lakes or something.
Islands is just a catchy name I guess. I always thought the markojs terms for it made sense, but are more technical / less catchy: they called it “full page hydration” -> everything needs to be delivered as js and “component level hydration” -> islands, only specific component sub-trees need to be hydrated.
Then “sub-component level hydration” would be resumability like in qwik where only events and their dependencies get serialised as client js.
Re: Cloudflare acquires Astro
#268Earlier quoted context omitted.
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.
Well, hopefully more like Go's relationship with Google? The company that pays the bills is their first and most important customer, but as far as I can tell from the outside, the Go team makes its own plans and management doesn't pull rank.
Definitely!
Re: Cloudflare acquires Astro
#269> 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…
What is the preffered way to do the opposite now? Not every webapp should be architected as an website.
Vite + React is the go-to recipe.
Re: Cloudflare acquires Astro
#270Earlier quoted context omitted.
The key difference between islands and what we used to do back in the day (js on a static page) is that with an islands approach you architect your site with a components-driven approach where everything encapsulates the js/css/html it needs, then you mark it as an "interactive" island if you actually need client-side js to run – the code is the same, but it either runs only in the server (default) or in both server…
You can do this with just about any programming language or scripting language that can render HTML on the server + plain HTML and JS. You could do this with PHP 30 years ago.
You could and yet nobody did.
You need to give credit to a project like Astro that takes a pattern, popularizes it and makes it straightforward to adopt via a framework.