[imh]

When react already has to be "modernized" I become thankful that I don't work in JS land. I honestly don't think I could keep up and remain happy.

[boubiyeah]

Not sure what you mean. React is 5 years old. Frontend development is more volatile by nature as devices changes, UX guidelines change, etc but overall React was very stable during these years.

But even Java changed A LOT in 5 years...

You always have to keep up as a developer.

[a13n]

And honestly, you don't really have to keep up with the latest version of React. We're still on 15.4 – almost 2 years old! Works great for us.

[acemarke]

Out of curiosity, anything preventing you from upgrading to 16.x ?

[a13n]

We're running a startup and upgrading React just isn't a priority.

[Klathmon]

You should read the link, these changes are less "modernizing" the API, and more doing the internals, many of which haven't changed since 2013.

In that process there will probably be some breaking changes, but Facebook has some insane number of components they use internally, so they try to never make any breaking changes that can't be automatically migrated.

[svachalek]

Changing className -> class and onChange -> onInput is going to affect practically every React component ever written.

They seem to have opposite rationales (class is less pedantic and onInput is more pedantic) and I expect at least one of them will get dropped along the way but we'll see.

[Klathmon]

They almost always provide codemods which can automatically convert a codebase for you, and they work pretty damn well.

And while I'm not sure if I'm on board with all of the changes, I'm in no way worried about having to do anything instantly.

[madeofpalk]

The rationale seems to be "default to plain html/dom" where possible.