The AI cost of JavaScript frameworks

(nolanlawson.com)

18 points | by luu 2 hours ago

5 comments

  • neya 3 minutes ago
    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.

  • drnick1 9 minutes ago
    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.
  • tancop 33 minutes ago
    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.
    • vermilingua 24 minutes ago
      Can confirm Astro is very very pleasant to use, and the escape hatches for when you do need something a bit more heavy hitting feel very well designed.
  • usernametaken29 18 minutes ago
    Angular sucks, I always knew it, and now we have some data that it’s broken even for agents. I’m not surprised
  • BatchJob 37 minutes ago
    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!