React is mature. The trick is to not get distracted by shiny things. I still think the whole thing is so overblown. There’s a lot of choice, great! That doesn’t mean you can’t pretend there isn’t.
Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
61–70 of 136 posts
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#62It’s interesting seeing so many comments about stabilization around React. It’s not wrong per se, but it’s also not reflective of what I see from the FE community elsewhere. I see a ton of interest in newer frameworks like Astro. Solid has been growing at a steady pace. Qwik is gaining steam. Even older frameworks like Angular and Preact are evolving, eg adopting more reactive features. Vue and Svelte are going strong, albeit probably not gaining much new traction. And people are creating new frameworks (whether for education/demonstration or to introduce new ideas) or building new paradigms on existing ones (even on React, be it Preact Signals or Blockdom).
I think the reason these aren’t prominent on HN is because the community here is overwhelmingly skeptical of, if not hostile to, new developments and exploration in the FE/JS space… and because the FE/JS community knows that and is likewise reticent to subject itself to that.
That said, it is true that React is a formidable incumbent, and that quite a lot of the space has coalesced around it. I don’t think that’s set in stone, I even think there’s at least some churn coming sooner rather than later. But I don’t expect that to make huge waves on HN unless and until it’s well underway.
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#63React won. Angular is officially deprecated, and the others are distant also-rans at this point. React Native has also almost completely taken over iOS development. Thank god we can all just agree on a baseline to work from finally.
Did react win? Or did it become the foundation for Next.js? We're using Vue here and missed the memo about it being an also run :)
>We're using Vue here and missed the memo about it being an also run :)
I don't hate Vue and I wouldn't judge anyone for choosing it, but my question is... why? It just seems like that entire community is set on reinventing every React feature with a two year delay.
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#64So what I’m getting from reading so many comments here… Did react hooks just totally alienate nearly everyone?
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#65Earlier quoted context omitted.
You can still use just React. No one is forcing you to use Next or Remix
No one is forcing you, but the React docs say "If you want to build a new app or a new website fully with React, we recommend picking one of the React-powered frameworks popular in the community. Frameworks provide features that most apps and sites eventually need, including routing, data fetching, and generating HTML." So, it going to be difficult to choose pure React with that kind of statement.
Even using React v5 without a state library for a large app was bonkers back then, regardless of what the library maintainers said.
At some point you will have some state that transcends the UI and trying to shove it into React UI component does not make sense.
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#66It’s interesting seeing so many comments about stabilization around React. It’s not wrong per se, but it’s also not reflective of what I see from the FE community elsewhere. I see a ton of interest in newer frameworks like Astro. Solid has been growing at a steady pace. Qwik is gaining steam. Even older frameworks like Angular and Preact are evolving, eg adopting more reactive features. Vue and Svelte are going stron…
I think there are a lot of frameworks on the edge of viability, but the bar is a lot higher than it used to be for front end tooling. React(70%), Angular(25%), and a little bit of Vue.js(5%) is the market for front end positions with React owning the Lion's share. There are always new things being built, but being used is different.
The React team has done a great job of being generic enough for a broad range of use cases. As new use-cases arise, someone can build a new framework to support it. SSR has gotten much more popular than the SPA style, and the core React team has moved to support it with server side components.
If they can continue to follow the innovators, React will continue to dominate the front end landscape.
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#67So what I’m getting from reading so many comments here… Did react hooks just totally alienate nearly everyone?
I'm not a fan of hooks (and the endless blog posts and opinions that hooks somehow were the invention of functional coding), but react server components did a lot of people in. The default expectations being that react frontends have a node backed isn't how much people use react.
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#68Earlier quoted context omitted.
haha, I basically feel this way about Svelte/Kit. It's not mature, but the surface is so small and learning curve so pleasant that it's our go to choice now for internal webapps. (We have no external webapps because my company, funny enough, builds a JavaScript framework!)
Doesn't sound like a very promising company if your own developers rather use a different framework than dogfood their own. Isn't that kind of admitting defeat?
We develop and sell a visual Diagramming library, not an SPA framework. There is no overlap.