[plugin-baby]

Are you recommending Next.js for its longevity? My experience over the last 18 months is that every new version introduces breaking changes. I wouldn’t want to come back to a Next.js project in 5 years and have to deal with migrating to Node.js v32 and whatever Next.js has broken in the meantime.

[s4i]

Don’t get me wrong, I’m not a Next.js fan either. Could’ve widened my list of examples to any SPA libraries and server-side JS frameworks. I just wanted to highlight the issue with the analogy: unlike some criminal a police officer is using force against, the nature of issues to be tackled in most software projects will keep changing.

[erhaetherth]

Better choose ExpressJS then. They still haven't quite made it to 5.0 since they started in 2014.

[yungporko]

that is going to be your experience no matter what you use if you want some horrible bloated frontend framework, or in this case, a horrible bloated framework for a horrible bloated front end framework.

will we get a next.js framework to make it easier to use next.js to make it easier to use react to make it easier to use javascript in the near future?

please for the love of god stop enabling these people.

[plugin-baby]

I haven’t had similar issues with React, and I been using it much longer - Next.js is a special case.

[erhaetherth]

React itself has been pretty smooth, and I've been using it since 0.14. Not on any massive projects mind you, but still.