271–280 of 409 posts
Astro is amazing. I've been using it for a couple of years now. Initially only for static sites but now I'm building the UI of all my web projects with it. I wonder if there will be some sort of collab between Hono and Astro given that Yusukue also works at Cloudflare.
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.
Nextjs doesn’t really work on cloudflare with the latest versions. There is an adapter but it’s buggy as hell. The direction is also likely to continue: https://omarabid.com/nextjs-vercel Source: I use cloudflare and used to run my app there (nextjs) and had to do a migration to vite.js. So the way I see it, this is cloudflare response to vercel.
Cross fingers that CloudFlare never try similar lock-in games, now that they control Astro?
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 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…
It'll be interesting to see where Astral ends up landing on that; afaik they have a small team and have only raised seed money, but who knows.
Earlier quoted context omitted.
They can stay open source, but stop putting any effort into supporting deploying to cloudflare's competitors, including accepting PRs for such improvements. Or they could add features that only work if you deploy via cloudflare. I also take anything said in an acquisition announcement with a grain of salt. It is pretty common for companies to make changes they said they wouldn't a few years after an acquisition.
Once again, it’s a static site builder. How, exactly, would they “stop supporting deploying to cloudflare’s competitors”? Be specific.
Earlier quoted context omitted.
They get to make Astro -> Cloudflare the default publishing pipeline. Sure users may pick something else, but even if a small % stick with Cloudflare that's an overall win.
I expected something clearer in the blog post about deploying Astro on Cloudflare Pages, as I imagine many Astro users (like me) are on Netlify. I think every deployment pipeline having it's own preferred UI framework (and CMS, and cloud-DB solution) makes a lot of sense.
I’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…
Earlier quoted context omitted.
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 dependencie…
Earlier quoted context omitted.
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.