4 ms·

I don't want to hate on Next, because I do like using the framework, but a new major version every 5 months for the lifetime of the project? How does anybody ac

I don't want to hate on Next, because I do like using the framework, but a new major version every 5 months for the lifetime of the project? How does anybody actually develop an application when you have to spend so much time keeping your framework up to date?

eyelidlessness 5y ago
To be fair, some of these updates are more significant than others. This one is probably the biggest since I first tried Next. React Server Components has the potential to make me consider using Next for static (MPA) sites again, which I’d previously written off because of the double payload problem.
swyx 5y ago
the major versions are mostly marketing new features. Next has been pretty conservative about how it deprecates APIs, i'd wager many Next.js 8 apps could just be updated to 12 with no change
gherkinnn 5y ago
Next has proven to be very backwards compatible to me. Even large steps, like moving from a server to handle routing (and i18n) to dynamic routing or that whole SSR business were bug chunks, yes. But in the right direction and without blowing up in my face. And could be adopted incrementally and in our own time.
Rauchg 5y ago
Stories like this[1] are not uncommon: > One of our users upgraded from Next.js 2.0-beta to 11 in 5 minutes. > As @timneutkens said in the Q&A, Next.js incrementally improving without breaking changes is worth the investment. If this is not the case, please let us know. We try to be very careful around this, and always leave breadcrumbs for easy upgrades in the DX if we absolutely must change something to move the project forward. [1] https://twitter.com/rauchg/status/1405241003653484546 https://twitter.com/rauchg/status/1405241003653484546
- throw123123123 5y ago
  I've done at least 20 upgrades (user since next 1.0) and it is getting easier and easier to migrate.
- tunesmith 5y ago
  This was not our experience earlier this year. We experienced a sequence of breaking changes in various dot-releases that led us to not being able to upgrade from 10.0.6 until 11.0.1 came out. Basically every single release in the 10.1.x and 10.2.x lines were unusable for us. We're very cautious about upgrading now. It's part of why I suggested this issue: https://github.com/vercel/next.js/issues/26827 https://github.com/vercel/next.js/issues/26827
  - Rauchg 5y ago
    Thanks for the feedback. I’ll bring this to the team

eyelidlessness 5y ago

To be fair, some of these updates are more significant than others. This one is probably the biggest since I first tried Next. React Server Components has the potential to make me consider using Next for static (MPA) sites again, which I’d previously written off because of the double payload problem.

swyx 5y ago

the major versions are mostly marketing new features. Next has been pretty conservative about how it deprecates APIs, i'd wager many Next.js 8 apps could just be updated to 12 with no change

gherkinnn 5y ago

Next has proven to be very backwards compatible to me. Even large steps, like moving from a server to handle routing (and i18n) to dynamic routing or that whole SSR business were bug chunks, yes. But in the right direction and without blowing up in my face. And could be adopted incrementally and in our own time.

Rauchg 5y ago

Stories like this[1] are not uncommon: > One of our users upgraded from Next.js 2.0-beta to 11 in 5 minutes. > As @timneutkens said in the Q&A, Next.js incrementally improving without breaking changes is worth the investment. If this is not the case, please let us know. We try to be very careful around this, and always leave breadcrumbs for easy upgrades in the DX if we absolutely must change something to move the project forward. [1] https://twitter.com/rauchg/status/1405241003653484546 https://twitter.com/rauchg/status/1405241003653484546

throw123123123 5y ago
I've done at least 20 upgrades (user since next 1.0) and it is getting easier and easier to migrate.
tunesmith 5y ago
This was not our experience earlier this year. We experienced a sequence of breaking changes in various dot-releases that led us to not being able to upgrade from 10.0.6 until 11.0.1 came out. Basically every single release in the 10.1.x and 10.2.x lines were unusable for us. We're very cautious about upgrading now. It's part of why I suggested this issue: https://github.com/vercel/next.js/issues/26827 https://github.com/vercel/next.js/issues/26827
- Rauchg 5y ago
  Thanks for the feedback. I’ll bring this to the team