News for hackers. Stuff that matters.
Re:Why developers need to be able to identify technologies w... by djstein on Monday June 25, 2018 @12:48PM (#17393798)
I'm not sure if you actually have ever used React but every single major version update is non breaking. The topics discussed in the link provided are discussing how an internal library is being updated (Context API) and how these functions are being depreciated in version 17 (https://reactjs.org/blog/2018/03/27/update-on-async-renderin...). The above depreciations are functions that typically should not be used in a v16 React application anyway! Using them typically means there lies a bug in your props updating logic.
Re:Why developers need to be able to identify technologies w... by flukus on Monday June 25, 2018 @08:30PM (#17397036)
> I'm not sure if you actually have ever used React but every single major version update is non breaking.

That would be fine if they were making major releases every 2+ years, when you release a major version on average of 3 times a year it's incredibly unstable. A typical upgrade will be jumping several versions.

Re:Why developers need to be able to identify technologies w... by gr__or on Thursday June 28, 2018 @06:06AM (#17415523)
A major version change of React is different from a major version change in Angular. I upgraded several React apps of variying sizes from 14 to 17 over time and none of these upgrades took more than an hour.

Don't get confused by the version labeling scheme.