@muan I think Astro is better if you need to make little dynamic parts in the pages (what they call "Islands architecture"). Jekyll and 11ty both seem fine to jam out some web pages, but it seems weird to rebuild everything so much.

@muan I'd say try the Astro tutorial first, unless you have already done it and really don't like it. Once you get to the routing and rendering of Markdown files, it just kind of works. It would not be the best if you have 100k posts, but I think that is an edge case.

@muan @slightlyoff you're right. I've written some pretty big ones, GitHub size or worse (meaning higher traffic).

A lot of that stuff happened because you had to write C++ or at least pretty advanced JVM/C# code to really make it work. If it was Python or Ruby... making the client do it JS made sense.

Now, there's Rust, Go, and all the older ones are better too. I have done all of them. Astro seems close to the approach you're describing here.

@slightlyoff It's kind of sneaking through. I thought this one was funny:

@slightlyoff Your position is not controversial, although sometimes you troll those folks. To me, it’s:

https://www.w3.org/2001/tag/doc/leastPower.html

You can even see this in bulid systems, where the build graph becomes unnecessarily opaque, because of CSS-in-JS etc.