Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloudflare acquires Astro

astro.build

Post reply on HN
Print view View original

181–190 of 409 posts

Re: Cloudflare acquires Astro

#181

Post by efilife »

charleszw wrote: post #76
mpeg wrote: post #37

Earlier 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…

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?

Re: Cloudflare acquires Astro

#184

Post by mattgreenrocks »

Hope that SSR remains first class as time goes on. I think Astro’s DX is superb overall, and am bullish on server-rendered components in MPAs with a sprinkling of hypermedia libs for better UX.

Some features of my SSR-based side project feel like I had to hack them on, such as a hook that runs only on app start (hacked in via middleware) or manually needing to set cache control headers for auth’d content.

All in all, really happy with it. And it isn’t next.js.

Re: Cloudflare acquires Astro

#185

Post by __jonas »

MatthewPhillips wrote: post #177
__jonas wrote: post #119

Earlier quoted context omitted.

No, not in particular, I just like Svelte's compilation-based approach, but Alpine definitely looks nice. When the client side interactivity is very contained and small in scope I also quite like just using plain JavaScript without a framework.

Sorry we haven't fixed this issue sooner. In this case it's a complicated CSS issue, but nevertheless I've got a fix I'm working on here: https://github.com/withastro/astro/pull/15227

Wow! That's a pretty impressive turnaround time from my comment to a PR, thanks for your work. I'll be happy to include this in my projects.

Re: Cloudflare acquires Astro

#186

Post by taraindara »

cornholio wrote: post #160
mpeg wrote: post #22

Earlier quoted context omitted.

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, cloudification: lock the customer into a complex cloud dependent solution they can't easily migrate to some other commodity infrastructure provider.

The easier/convenient a cloud makes it for a business to use, the more the industry will continue to trend towards lock in

Re: Cloudflare acquires Astro

#187

Post by jjmarr »

mpeg wrote: post #22
philipallstar wrote: post #6

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…

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/

Re: Cloudflare acquires Astro

#188

Post by mattgreenrocks »

jtbaker wrote: post #59
mpeg wrote: post #22

Earlier quoted context omitted.

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…

> Nextjs has no support From what I remember, you can't even run a NextJS app through vite?

This is insane to me, and validates my irrational dislike of next.

Re: Cloudflare acquires Astro

#189

Post by array_key_first »

philipwhiuk wrote: post #12
koakuma-chan wrote: post #9

I am very disappointed with Astro. Who is this framework for? It's been years, and they still don't support unit testing Astro Actions. They still don't support inter-island communication. "Astro v6 is around the corner" - and the only changes are 1. refactored CLI (why? it's perfectly fine) 2. bumped zod to v4 It's great if you want to build a blog or something, but it's definitely far from great for building apps .…

If all you are writing a blog and you're not using Substack or Squarespace or any of the other million blog hosting options you're crazy IMO.

You become beholden to these platforms and they're inherently not portable. There is risk here, and given the track record of Internet companies I think it's fair to say the risk is not worth it for many people.

Your costs could explode, or worse, the business could go under and you lose all your shit.

Post reply on HN