Hacker News new | ask | show | jobs
by Klathmon 2855 days ago
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.

1 comments

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.

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.

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