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

81–90 of 409 posts

Re: Cloudflare acquires Astro

#81

Post by koakuma-chan »

mpeg wrote: post #75
koakuma-chan wrote: post #66

Earlier quoted context omitted.

Astro component is your page's entry point. It's similar to React server component. The typical flow is to fetch data in it, and pass the data to client component written in React or whatever. You can also have pages that are Astro only, without any front-end framework.

Yeah, I know, but since by default the front-end islands are server-rendered with no hydration the lines are blurred between what you would use an .astro component for, and just using for example react. Personally I only ever use .astro components if I'm 100% sure I will never need any client side interactivity, otherwise it's just easier to ignore them.

I mean, you have to have an .astro file if you want your route to be picked up, and then import and use React components in that file. IIRC, you cannot just directly use React.

Re: Cloudflare acquires Astro

#83

Post by mpeg »

koakuma-chan wrote: post #81
mpeg wrote: post #75

Earlier quoted context omitted.

Yeah, I know, but since by default the front-end islands are server-rendered with no hydration the lines are blurred between what you would use an .astro component for, and just using for example react. Personally I only ever use .astro components if I'm 100% sure I will never need any client side interactivity, otherwise it's just easier to ignore them.

I mean, you have to have an .astro file if you want your route to be picked up, and then import and use React components in that file. IIRC, you cannot just directly use React.

Oh right, yeah I get what you're saying now. Indeed I think .astro templates make sense at the page level say to define a layout, and I actually like the syntax of stuffing the server js into a frontmatter style block, it's pretty nice.

Re: Cloudflare acquires Astro

#84

Post by csomar »

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.

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.

Re: Cloudflare acquires Astro

#85

Post by catoAppreciator »

mpeg wrote: post #64
__jonas wrote: post #45

Earlier quoted context omitted.

Yeah I suppose it's a tradeoff. I have had an excellent experience when not hydrating components at all, and I like their approach significantly more than other SSGs overall. My worry is just the massive scope of supporting integrations with all those frameworks AND its own .astro language / syntax AND server side rendering in addition to static generation.

To be fair, vite does a lot of the heavy lifting when it comes to supporting extra frameworks. If you look at the code required for astro to integrate with a new technology you'll see it's relatively straightforward. For example, here's all the code in the svelte integration: https://github.com/withastro/astro/tree/main/packages/integr...

Wow. Good callout.

Re: Cloudflare acquires Astro

#87

Post by catoAppreciator »

__jonas wrote: post #35

I like the idea behind Astro, I've used it for a couple websites here and there. I'm a bit worried about the complexity brought by Astro supporting all these different frameworks through its adapters, and how stable and maintainable those websites will be in the future. For instance: I've been using Astro with Svelte to build static sites with some components that require client-side interactivity. I really like that…

Any reason you didn't use alpine for client side interactivity? When I went down the "use a framework plugin in Astro" route, I found it too jarring and reverted to alpine which I found worked well enough.

Re: Cloudflare acquires Astro

#88

Post by tialaramex »

pjmlp wrote: post #57
MarkusAllen wrote: post #46

[flagged]

> Linux: 33 years old, runs the internet, community-funded Only in dreams, it took off thanks to the likes of IBM that decided it was a way to save costs on their UNIX development efforts, many key projects have been founded thanks to Red-Hat Enterprise licenses, nowadays also part of IBM. GCC, clang, GNOME, Linux kernel, systemd, CUPS, AMD/NVidia drivers, have plenty of big corp money. From https://en.wikipedia.org/…

It's still the community when the community is via corporations.

Corporations are just groups of people. Pure grass roots "We collect the money, anonymously in cash shaking a bucket at our annual fundraiser" does not work at this scale. Even Zig, which I'm guessing is about as far away from "It's all just owned by an inhuman corporation" as you could ask for, does have big ticket corporate donors. So does ISRG (Let's Encrypt) or the EFF.

Venture Capital is a bad fit, that's the conjecture here. VC funding for infrastructure is a mistake because that big pay day won't happen if you did it correctly. That doesn't make VC inherently bad, or projects like Linux inherently defective, the claim was that it's just a bad match, like how an Irish Stout doesn't pair well with a subtle tomato and angel hair pasta dish.

Re: Cloudflare acquires Astro

#90

Post by sieep »

fnoef wrote: post #68

Welp, I'm worried. I like Astro, but maybe it's time to make my own SSG, to not ever end up in the hand of a few big-sharks that consolidate and enshittify everything.

jumped on the same train, still using astro in production but on the side im using Elixir to create an SSG to use moving forward for anything new.
Post reply on HN