undefined | Better HN

0 pointsmeiraleal2y ago0 comments

That's what you get for working in a famous company that took over an open source software.

If the destruction of React by Vercel paid your bills and you feel disrespected by my total despise for this get rich fast schema (a la crypto rugpulls), that's a problem for you to solve, not me.

Edit: but in reality I'm happy and thankful to Vercel for imploding React, it helped me to finally check that there are so many better options nowadays.

0 comments

junon2y ago

How did Vercel "destroy" React? How are they a "get rich quick" "rugpull"?

Respectfully, you have no idea what you're talking about.

reducesuffering2y ago

Dan Abramov, de facto lead for React, said that the React team was driving the vision behind the new features in React. Vercel just said, "how can we help? You guys think server components are great, ok, we'll make them first class as that's where the React ecosystem is headed."

Vercel is doing nothing but trying to improve DX for all the things people complain about React.

aurareturn2y ago

I started using Next.js in 2017. It made React a real production framework. Prior to Next.js, React was hard to setup and maintain and hard to make it go fast (on first load). Next.js solved the worst React problems.

I don't think it ruined React at all. I think it helped React gain in popularity - which you might interpret as "destruction".

meiralealOP2y ago

> Prior to Next.js, React was hard to setup and maintain

No, it wasn't. Now it is an engineering process.

> I started using Next.js in 2017. It made React a real production framework

In 2017 I had React projects in production for years.

> React was hard to setup and maintain and hard to make it go fast (on first load)

And it only got worse and the overengineering to make it looks fast in the first load is not worth it as modern JS frameworks are faster than React out-of-the-box.

> I don't think it ruined React at all. I think it helped React gain in popularity

That's not what stackoverflow's Insights says[0]. Looks like a free fall for me.

0. https://insights.stackoverflow.com/trends?tags=reactjs

junon2y ago

> In 2017 I had React projects in production for years.

I doubt that. React wasn't stable until 2015, and wasn't mainstream until 2016.

> And it only got worse and the overengineering to make it looks fast in the first load is not worth it as modern JS frameworks are faster than React out-of-the-box.

Again, Next.js != React; the former builds on the latter, it doesn't replace it nor does it claim to be the same thing. I'm not sure why you keep conflating the two.

> That's not what stackoverflow's Insights says[0]. Looks like a free fall for me.

Perhaps you shouldn't bury the lede here. I'm also not entirely sure what your argument is, or why you hold such strong emotions without making your opinions very clear.

https://insights.stackoverflow.com/trends?tags=reactjs%2Cnex...

1 more reply

j / k navigate · click thread line to collapse

0 comments

junon2y ago

How did Vercel "destroy" React? How are they a "get rich quick" "rugpull"?

Respectfully, you have no idea what you're talking about.

reducesuffering2y ago

Vercel is doing nothing but trying to improve DX for all the things people complain about React.

aurareturn2y ago

I don't think it ruined React at all. I think it helped React gain in popularity - which you might interpret as "destruction".

meiralealOP2y ago

> Prior to Next.js, React was hard to setup and maintain

No, it wasn't. Now it is an engineering process.

> I started using Next.js in 2017. It made React a real production framework

In 2017 I had React projects in production for years.

> React was hard to setup and maintain and hard to make it go fast (on first load)

And it only got worse and the overengineering to make it looks fast in the first load is not worth it as modern JS frameworks are faster than React out-of-the-box.

> I don't think it ruined React at all. I think it helped React gain in popularity

That's not what stackoverflow's Insights says[0]. Looks like a free fall for me.

0. https://insights.stackoverflow.com/trends?tags=reactjs

junon2y ago

> In 2017 I had React projects in production for years.

I doubt that. React wasn't stable until 2015, and wasn't mainstream until 2016.

> And it only got worse and the overengineering to make it looks fast in the first load is not worth it as modern JS frameworks are faster than React out-of-the-box.

Again, Next.js != React; the former builds on the latter, it doesn't replace it nor does it claim to be the same thing. I'm not sure why you keep conflating the two.

> That's not what stackoverflow's Insights says[0]. Looks like a free fall for me.

Perhaps you shouldn't bury the lede here. I'm also not entirely sure what your argument is, or why you hold such strong emotions without making your opinions very clear.

https://insights.stackoverflow.com/trends?tags=reactjs%2Cnex...

1 more reply

j / k navigate · click thread line to collapse