martpie
Joined 8 years ago
Joined 8 years ago
It seems they just drafted a new release to communicate the groups of change from the previous releases.
I am not 100% sure to understand the hostility towards such a feature, that seems accessible only via a user-action.
It makes UI changes much much easier to deal with.
But since maybe 1-2 years, I am back and betting on React for most of my serious projects (for the ecosystem, the ease of hiring, etc), but the most important point is the following:
React backwards compatibility is really good, and will stay so for a good reason: a LOT of Meta’s UI code is using old features (classes syntax etc), and Meta cannot afford to break those. If there are breaking changes, they must be “codemodable” (so, usable by everyone).
Meaning in terms of stability, I know my codebase today will still work fine in years ( or upgrade-able with minimal efforts). Of course there will be new shiny features, but I or my team will not have to rewrite old code all the time following tedious migration guides.
disclaimer: I am kind of biased as I work at Meta, but far from React.
JS developer, maker of Museeks. Stupid and arrogant french in my spare time.