AI kills frameworks
Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
121–130 of 136 posts
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#122React is now the de facto choice and much less painful than past de facto choices, is my take on why. It has a mature and healthy ecosystem, and its relatively small surface makes it easy to learn and predictable, while declarative GUI in general is low on footguns compared to ye ol two-way data binding. Many of the competitors springing up define themselves in terms of React, either as an improvement or a foil. But…
Hold that thought. Many people are saying React has jumped the shark with the complexity of server components and tight coupling with favored frameworks like Next.js I wouldn't be surprised to see some movement toward simpler but equally robust frameworks like Vue or Svelte.
Or SolidJS which uses Signals.
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#123Earlier quoted context omitted.
Hold that thought. Many people are saying React has jumped the shark with the complexity of server components and tight coupling with favored frameworks like Next.js I wouldn't be surprised to see some movement toward simpler but equally robust frameworks like Vue or Svelte.
Or SolidJS which uses Signals.
I actually really enjoyed programming with Qt in C++ using "signals and slots," about ten years ago for a school project. Perhaps it was ahead of its time.
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#124So what I’m getting from reading so many comments here… Did react hooks just totally alienate nearly everyone?
Not a single frontend dev I know in real life has had the same negative reaction about hooks that I often see on HN.
I remember some people taking a little longer to adopt them either cause it wasn’t necessary or cause it didn’t click right away, but eventually everyone learned how to use em, and no one complains about them cause they’re just a tool you use if you use React (which is the framework of choice for most companies).
Honestly, the reaction I often see from HN around most frontend topics usually doesn’t match what the frontend and full stack devs I interact with regularly are saying. Don’t get me wrong, it’s not like we all love React and want to switch state management libraries every week; it’s that React is fine, the ecosystem is fine, and we specifically don’t use every library that comes out week after week.
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#125Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#126Similar to Spring in Java, React became de-facto a standard having now a thriving ecosystem and an enormous community. This is actually probably the largest community if you compare it to any other framework or programming language out there.
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#127React is now the de facto choice and much less painful than past de facto choices, is my take on why. It has a mature and healthy ecosystem, and its relatively small surface makes it easy to learn and predictable, while declarative GUI in general is low on footguns compared to ye ol two-way data binding. Many of the competitors springing up define themselves in terms of React, either as an improvement or a foil. But…
> React is now the de facto choice
I contract for a few companies and everyone seems to have a different take on the industry standard.
React may well be biggest, but I don't think it's possible dominance is the reason there are fewer framework posts on HN recently.
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#128[deleted]
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#129I wonder what will be the next mindless thing related to AI on which programmers will be wasting their days reinventing the wheel every 3 months. Langchain and such?
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#130Earlier quoted context omitted.
I’m starting to feel the same way. React’s big selling point when it came out was that it was “easy to reason about”, and that was true at the time. With hooks, server components, and 10,000 different strategies for managing state and side effects, I can’t say React is easy to reason about anymore. We can do things now that were impossible back then, but now we need to do even more than that, and it feels like it’s t…
Hooks are particularly bad to reason about. I can't figure out why hooks seems to be the official Way, it just leads to a bunch of spaghetti functions. The old object-oriented approach might feel old and creaky, but OOP was invented for user interface. Functional programming, not so much.
Or emit events and have listeners for them. Something more similar to message passing and, incidentally, one of the original definitions of OOP.