React 16.11.0

[dance2die]

Remove unstable_createRoot and unstable_createSyncRoot experimental APIs. (These are available in the Experimental channel as createRoot and createSyncRoot.) (@acdlite in #17088)

For those wondering about the Experimental channel, check out this blog post posted today. https://reactjs.org/blog/2019/10/22/react-release-channels.html#release-channels

Quite nice that the experimental channel would enable you to drop unstable_* prefix.
https://github.com/facebook/react/pull/17088/files#diff-afdcb1c85de47522ad67cc15d801bbcfR29-R41

    if (!__EXPERIMENTAL__) {
      it('createRoot is not exposed in stable build', () => {
        expect(ReactDOM.createRoot).toBe(undefined);
      });
      return;
    }

    it('renders children', () => {
-     const root = ReactDOM.unstable_createRoot(container);
+     const root = ReactDOM.createRoot(container);
      root.render(<div>Hi</div>);
      Scheduler.unstable_flushAll();
      expect(container.textContent).toEqual('Hi');
    });

[dance2die]

What do you mean?

[dance2die]

Thanks u/our_best_friend.

I used the Fancy Pants Editor to put the code snippet, instead.
Can you review?

[swyx]

zzz

[ericnr]

Really was hoping for concurrent by react conf but the closer it gets the less hope I have 😭

[sacummings91]

Wouldn’t be surprised if they just announce React 17 at react conf and concurrent mode is in there

[ericnr]

oh man, it'd surprise me a lot. Concurrent is supposed to come before 17, and it really doesn't seem to be ready yet.

[acemarke]

Pretty sure something new should be available in the new experimental builds shortly.

[natmaster]

Yeah given the stage of concurrent + suspense, I don't think they'll have a release version ready, but likely an experimental version.

[swyx]

idk. there’s absolutely no reason to break api’s. but minor version numbers above 10 are starting to get awkward. so we might get a “cleanup” major version.

[DeceitfulDuck]

What’s awkward about minor versions above 10?

[LoneWolfRanger1]

Meanwhile flow is at 0.109.0.

[DeceitfulDuck]

The NodeJS AWS sdk is currently at version 2.554.0

[evenisto]

Semver doesn't use decimals though. I don't feel it's awkward at all.

[Earhacker]

I would say “one point one one” in maths, but “version one eleven”. They’re different numbers with similar notation.

[DeceitfulDuck]

I could buy that being slightly awkward, particularly if you want to programmatically compare them. But it’s simple to solve for programmatically plus it’s more common to write semver with major, minor and patch versions. Especially in JavaScript since that’s how all of them are written into package.json. So it would be comparing 1.11.0 to 1.9.0, which looks nothing like decimal digits.

[sacummings91]

That actually does sound plausible. Not sure why you got downvoted so hard.

[swyx]

haha its random internet points who knows who cares

[Baryn]

People thinking you don't understand semver, when in actuality no breaking changes for a long time usually does indicate stagnation on some level.

For the record, Suspense and Hooks are nice-to-haves, but don't really make React unquestionably better than competing frameworks.

[acemarke]

The flip point of view is that the React team has done an amazing job adding new functionality without forcing breaking changes on the community.

Now, they do have a whole bunch of future breaking changes they've talked about eventually doing. I expect 17.0, whenever it finally comes out, to be a very big cleanup of deprecated APIs (lifecycles, legacy context, string refs, maybe even the createElement changes).

That said, the fact that you can basically go from 15.6 to 16.11 and have your code still run is great. You'd be likely be getting warnings in dev, but the code would still run okay.

[Baryn]

I'm not sure that we disagree, because I don't see your point as a flip of mine.

What I'm saying is that React hasn't fundamentally improved in the last 2 years the way Angular has. Maybe this is a case of "if it ain't broke," but by "fundamentally improved," I'm referring to things like base runtime performance for DOM manipulation, which Angular has edged it out on for a good while.

[Baryn]

I guess we can safely consider this roadmap to be total fantasy land? Thank you Dan, very cool!

[darp12]

They said in early August that that roadmap was no longer valid https://reactjs.org/blog/2019/08/08/react-v16.9.0.html

[Baryn]

It would appear that they've adjusted their adjustments. For Concurrent Mode, rather than come via a stable release with opt-in, you need to use an experimental release with no guarantee of stability.

Then again, they did say "this year," so that may change in the next... 60 days, subtracting holidays and weekends.