This reminds me of a lot of the buildup for Drupal 9. After experiences sometimes bordering on traumatic for users upgrading from 6 to 7, or 7 to 8 (which ironically was less streamlined than migrating from 6 to 8 because they wanted to get people off 6 and finally make it EOL), they opted to make 9 "as simple as updating a point release in D8."
There's still plenty in the works (e.g. concurrent mode, suspense for data fetching), and just look at how much has changed since v16 was released (completely new context API, hooks, etc.). But I think that they basically made it so those new features can essentially be "ready to go" in a future point release, just removing an experimental_ prefix if even that, without waiting for external API changes before the major version bump.
With that said, I'm definitely holding back on React Native for now, as it always rolls a little behind react-dom.
This reminds me of a lot of the buildup for Drupal 9. After experiences sometimes bordering on traumatic for users upgrading from 6 to 7, or 7 to 8 (which ironically was less streamlined than migrating from 6 to 8 because they wanted to get people off 6 and finally make it EOL), they opted to make 9 "as simple as updating a point release in D8."
Yeah, exactly. I think now the ecosystem is set and everything is smooth. That's why they let it be that way.
There's still plenty in the works (e.g. concurrent mode, suspense for data fetching), and just look at how much has changed since v16 was released (completely new context API, hooks, etc.). But I think that they basically made it so those new features can essentially be "ready to go" in a future point release, just removing an
experimental_
prefix if even that, without waiting for external API changes before the major version bump.With that said, I'm definitely holding back on React Native for now, as it always rolls a little behind react-dom.
Yes exactly. There's plenty of work but I think after hooks they are pretty much clear about their direction.