301–310 of 409 posts
I have always liked Astro. It also works great with AI tools since its combination of markdown and code. Was able to vibe code a quick blog template and deploy to cloudflare in minutes with an existing headless backend - https://sleekcms-astro-blog.pages.dev/
Websites should not be vibe coded.
Damn. What alternatives does HN recommend?
I 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.
Earlier quoted context omitted.
Definitely irrational. There are lots of logical reasons to dislike Next (like the fact that they pile new shiny bit on top of new shiny bit without caring about the regular user experience) ... but being mad that it can't run on Vite is silly. It's like being mad that Rails can't run on Python, or that React can't run on jQuery. Next already has its own build system, so of course it doesn't work with another build s…
Isn’t the next.js build system known for being slow/memory hungry?
Earlier quoted context omitted.
HTML. Unironically have been migrating my static pages (from Nextjs and Eleventy) to plain HTML and love it. Of course depends on your use case if that is feasible.
Plain html has two things going against it. First, it doesn't have any provisions for code reuse. So, if you have multiple pages that use the same header, same footer, or same navigation menu, your options are either to copy-paste it (gross), or to build the final html out of smaller pieces, at which point you've reinvented either a static site generator or a web server. Second, if you write long stretches of text, t…
Earlier quoted context omitted.
Seems like an obvious thing to call out for people (like me) who don't know.
So something like "now that we own Astro, all of you using Netlify should start migrating to Cloudflare Pages"?
Earlier quoted context omitted.
So when folks say they want to see big companies invest in open source, this is what that looks like. CF could have kept coasting on what Astro was building, but instead they are paying for it. But in return they get a lot of control.
Well, hopefully more like Go's relationship with Google? The company that pays the bills is their first and most important customer, but as far as I can tell from the outside, the Go team makes its own plans and management doesn't pull rank.
Earlier quoted context omitted.
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.
I 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 in Astro would make it easier to use? Or, what makes it more complex to use than you'd like? We're always open to feedback!
Generative AI is not suitable for building content-driven websites because it lacks context to understand subjective user preferences.
Also, having .astro files to implement island functionality is unnecessary. Interactivity can be implemented with Javascript using web components.