Earlier quoted context omitted.
This is making me even less interested in trying Astro. Websites should not be vibe coded.
So.. just because a tool can be potentially mishandled (e.g. put in the hands of a toddler, which is basically what vibe code ends up being) because it's easy to use, you never want to take a look at said tool? That sounds like shooting yourself in the foot out of pure spite, but you do you.
Cloudflare acquires Astro
401–409 of 409 posts
Re: Cloudflare acquires Astro
#402Re: Cloudflare acquires Astro
#403I found that Vite does a great job of deploying static websites. All I had to do was add Vite as a dev dependency in my pacakge.json and make sure all the page routes in vite.config.js. I've been skeptical about trying Astro because it seems to have unnecessary complexity. Also, I don't see any evidence that Cloudflare is going to prioritize making Astro easier to use.
What are you doing about repeated content?
For repeated content where JavaScript is required, I use web components.
Re: Cloudflare acquires Astro
#404Earlier quoted context omitted.
I will also say encapsulating everything you just said in a single term, "islands," is a lot simpler and prettier to discuss. At least from my perspective, the naming also makes a lot of sense. Literal islands of interactivity surrounded by an ocean of static.
the naming is backwards then. An island is static, an ocean is not. See how it is a buzzword up to your interpretation?
And yet, we all know what it means. Language is fun.
Re: Cloudflare acquires Astro
#405I’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…
Out of curiosity, how do you become ‘exceedingly good’ at serving static HTML? By all accounts, they’ve centralised the delivery of this static HTML at several layers of the network stack, and you’re not getting static HTML anymore because some other part of the business fucked it up. The World Wide Web was serving static HTML for decades before Cloudflare came along. Open an FTP client, drag and drop, and boom - new…
If your traffic volume stays well below server capacity, the network connection is impeccable and throughput isn't a major factor in ISP costs, then the improvement is indeed negligible.
However, if the server or it's network ever experience congestion or disruption, or you simply face sheer volume, that's when CDNs shine.
Regional caches insulate clients from network or performance issues with your server or its connection. If you have high volume, they also drastically reduce traffic through the backbone which can reduce ISP costs, depending on your contract.
Like others say, this really applies to all static content, including static media, css and js.
I hear you ask, "how can you be exceedingly good at this?" Caching itself isn't tricky, but catching efficiently and effectively at such huge scales is. The fact that Cloudflare offers these services for FREE, is a pretty good (perhaps Faustian) deal.
Re: Cloudflare acquires Astro
#406Re: Cloudflare acquires Astro
#407I 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.
Static optimized sites take very little compute, and little queries.
Since they have the most used framework (nextjs), they made it more server-heavy and changed the paradigm to one where a single page is built up using multiple queries for even just the html.
They then made sure that self hosting that monstrosity is terribly complex for anything serious, and incompatible with the "serverless environment" of their own platform, unless you have devops maintaining it.
And then they severely overhauled the pricing and gimped the included limits. (We were on It could of course be a coincidence, but if that were the case, they would be very bad, yet lucky, business people.
100% will never put anything new on vercel and have been avoiding nextjs like the plague.
Re: Cloudflare acquires Astro
#408Earlier quoted context omitted.
For the perplex: e.g. is latin for "exempli gratia" = for example i.e. is latin for "id est" = that is
As someone who was perplexed, I've only heard perplex used in past tense (I was perplexed) so seeing "For the perplex" just made me confused as to what "perplex" meant and I had to do a further search to decipher this tree of comments haha
Re: Cloudflare acquires Astro
#409The real question is whether Cloudflare can maintain Astro's "framework agnostic" soul while being incentivized to push everyone toward Workers/Pages.