Yes, now it's full of LLM grifter type of shit.
Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
11–20 of 136 posts
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#12There was a point where over half of them were React and everyone seems satisfied with that.
All of the JS framework posts I do see are about how they don't like React. There are two kinds of frameworks, the kind people don't complain about, and the kind they use. So it seems people mostly settled on React. They're grumpy about it but it does the job and there seems to be no alternative compelling enough to complain about.
Compared to what we had before, react is pretty nice.
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#13React 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…
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!)
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#14React 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…
I believe WordPress choosing React as its frontend framework of choice further solidified this point.
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#15GPT knowledge cutoff is eons ago in js time. They all had to go back to React for it to write code for them :D
I think about this a lot. About how ChatGPT is perhaps cementing a lot incumbent tech right now. I wonder if the existence of these tools might actually slow down advances in frameworks, packages, libraries, etc...
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#16React 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 doesn't have a "relatively small surface" any more, because even the React team doesn't recommend that you use "just" React. It's all frameworks on top of React like Next or Remix, and those are more complex, have many involved concepts and come with footguns. I have seen many, many sites switch to Next and completely bungle it, making the user experience worse than it was before the change.
(Of course, even React itself has gotten fairly complex with Hooks, Suspense and the dreaded Server Components.)
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#17I see a lot less programming topics, in general.
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#18React 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 doesn't have a "relatively small surface" any more, because even the React team doesn't recommend that you use "just" React. It's all frameworks on top of React like Next or Remix, and those are more complex, have many involved concepts and come with footguns. I have seen many, many sites switch to Next and completely bungle it, making the user experience worse than it was before the change. (Of course, even Re…
> I have seen many, many sites switch to Next and completely bungle it, making the user experience worse than it was before the change.
What are some specific sites you've seen that adopted react and ended up worse as a result of it?
> doesn't have a "relatively small surface" any more, because even the React team doesn't recommend that you use "just" React
Isn't this evidence of it having a relatively small surface area that frameworks and other tools can build on top of, much like html, css etc?
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#19React 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.
Re: Ask HN: Anyone else notice that HN isn’t full of JavaScript frameworks lately?
#20I found a gut bacteria story here just the other day. Hackernews gonna hackernews.
But yeah, JS frameworks seem to have run their course. The corporate world appears to have settled on React. The new thing is, look what I did by futzing with AI.