|
|
|
|
|
|
by meiraleal
970 days ago
|
|
|
> I doubt that. React wasn't stable until 2015, and wasn't mainstream until 2016. I started using React before its 1.0 version. Your reasoning is exactly what's wrong with Vercel. Arrogant inexperienced people that think they know better, empowered by VC money. Together with some idealization of being the smartest people around makes you come with solutions like "use server" and throw tantrums when people say this is stupid for a frontend library. > 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. It is okay if you can't understand what I'm saying, it is difficult to get a man to understand something, when his salary depends upon his not understanding it. I also don't expect you to agree that the work you did contributed to an open source take-over for the sake of profit. Edit: I just did a research to see if Meta is adopting the amazing "use server" and no public information is available, only people discussing that they aren't. That says a lot about the applicability of this feature and the direction React is being leaded to. |
|
|
React was complete shit back then - especially the first load speed. It was not ready for "real" production. We basically built an internal framework on top of React for things like server side rendering (which no one did with React back then), above the fold loading optimization, developer experience, devOps on top of React. We basically built Next.js internally.
So no. It was not production ready for real performance-based websites. Next.js made it significantly better as soon as it came out.