HTMX is interesting.

I have most of my apps in it without much trouble.

One of my recent ones had a very complicated form and state management.

AI really struggled with HTMX in that use case.

Like the form might work but the page would take 30s to load. Or some state would randomly drop or a toggle wouldn't work after changing a dependency.

If I rewrote that in react it would have one shot it without a doubt. Some things are just better models for different problems.

For the record I eventually got enough tests in place to keep the agent honest and the HTMX version is now a lot faster anything I could have got out of react but yeah, it was an adventure.

This is buried at the end.

> My goal here is not to write the end-all-be-all benchmark for “I’m a vibe-coder, which framework should I choose?” The point of this post is to demonstrate that it’s possible in the era of AI coding to still make decisions based on evidence rather than vibes.

But it’s obvious that the article will be understood as a useful benchmark, so author probably should have addressed that point earlier and more thoroughly.

Taking the authors pov for a moment, they just showed you how to put all your criticisms to work in making a newer better benchmark :)

This benchmark is too simplified to be meaningful. The choice of a framework is rarely based on speed alone, it factors in other elements like the user's domain knowledge, long term maintainability and the framework's track record itself w.r.t security and development of features.

In this regard alone, it will make a lot of sense to spend extra $2 and 2 mins to trade off for a long-term maintainable codebase and code you can reason about than just something made quickly just to get it deployed fast.

In my personal use case, that would be Svelte 5 for me and I'm sure it will be something else for everyone.

Astro comes out on top with the best time, #2 lowest spend and zero client side JS. I know what I'm using for my next project.

htmx for the win, as always

Java script frameworks are just extra boiler plate that isn't needed in the age of ai-coding.

Server side page generation with a sprinkle of js will give you the same results with GBS less of packages and comple time

> in the agentic era, when developers are no longer typing code by hand

I hope I'll be the last person on Earth writing code by hand.

Interesting article. Kind of seems like you'd want a more complex task, there's not much differentiation here.

Interesting, I’m just sad svelte didnt behave better because of the LLM reading migration guide on every answer

I mean it just seems like even in the agentic era, you should know when to use the right tool for the right job. The site shown seems perfect for htmx style websites, so idk why you would use an SPA. Still very cool experiment, appreciate the data and human writing!

Nice to see Nuxt holding its own. Astro or Nuxt are my gotos for client work and personal projects.

Angular sucks, I always knew it, and now we have some data that it’s broken even for agents. I’m not surprised

Glad to see Astro doing well here. It's by far my favorite way to build sites of all kinds, both content rich MPAs, and react heavy web apps.

It is fairly obvious that it is all going to be some kind of React/JSX with tailwind.

where is jquery? :(

Just use plain HTML for God's sake. HN demonstrates very well that you can do plenty without some Javascript monstrosity. At the very least, make your your websites degrades gracefully when JS is turned off.

Unfortunately the author is not only correct about front end development vibes, but due to this state of affairs, I ceased to recognize browser based UIs as being software development at all. Too much browser tech is broken to call it software. As for agents, good for them!

[flagged]

[flagged]