Cloudflare acquires Astro
111–120 of 409 posts
Re: Cloudflare acquires Astro
#112Re: Cloudflare acquires Astro
#113[flagged]
Re: Cloudflare acquires Astro
#114Damn. What alternatives does HN recommend?
Then one is pretty much safe from framework tides.
Re: Cloudflare acquires Astro
#115Earlier quoted context omitted.
> CloudFlare is hardly "big tech" yeah, it's still losing money
[flagged]
thanks for the unrequested slop!
you know what GAAP stands for?
"generally accepted accounting practices"
so what does non-gaap mean?
"non-generally accepted accounting practices"
aka: bullshit
Re: Cloudflare acquires Astro
#116It's the first framework I recommend to web dev beginners, after they have built something with plain HTML and CSS.
Re: Cloudflare acquires Astro
#117Earlier quoted context omitted.
Netlify didn't buy Gatsby for the framework. They wanted the hosting business and the GraphQL thing. They said this at the time, and it's true. It was barely resourced. Cloudflare is only interested in the framework (because Astro has nothing else). Source/disclosure: I worked at Gatsby, Netlify, Astro and Cloudflare
Why did they want Gatsby's graphQL thing? What was attractive about it?
Re: Cloudflare acquires Astro
#118Earlier quoted context omitted.
Yeah, I'm not sure I understand why "islands" isn't just "bits of JavaScript on a static page". It feels like the "JavaScript as a Server Side Language" folk are just repeatedly re-inventing stuff that has been done a million times by other systems with a different back-end only with a new fancy name.
It has been funny seeing the tide come in and out now a few times. Though I will admit that each time, the ergonomics get better. AJAX as a pattern was pretty gnarly if you wanted to do a bit more than update a notification badge or comment box. There's a really nice pattern of using Custom Elements [0] for that sort of JS interactivity sprinkling. You can make your web application however you want, and when you want…
Re: Cloudflare acquires Astro
#119I 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.
When the client side interactivity is very contained and small in scope I also quite like just using plain JavaScript without a framework.