react-future

Specs & docs for potential future and experimental React APIs and JavaScript syntax.

Web Development Learning & Reference

Explore on GitHub Read Hacker News discussions

10Distinct people

12Mentions

0Explicit recommenders

2.8KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Specs & docs for potential future and experimental React APIs and JavaScript syntax.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

react/react · linked in 2 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month12 dated mentions

Observed mentions: 2014-07-21 16:30:50 UTC to 2015-12-29 20:09:11 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
Jul 2014	2014-07-01 00:00:00 UTC	2014-08-01 00:00:00 UTC	1	0	1
Aug 2014	2014-08-01 00:00:00 UTC	2014-09-01 00:00:00 UTC	0	0	0
Sep 2014	2014-09-01 00:00:00 UTC	2014-10-01 00:00:00 UTC	0	0	0
Oct 2014	2014-10-01 00:00:00 UTC	2014-11-01 00:00:00 UTC	1	0	1
Nov 2014	2014-11-01 00:00:00 UTC	2014-12-01 00:00:00 UTC	1	0	1
Dec 2014	2014-12-01 00:00:00 UTC	2015-01-01 00:00:00 UTC	0	0	0
Jan 2015	2015-01-01 00:00:00 UTC	2015-02-01 00:00:00 UTC	3	0	3
Feb 2015	2015-02-01 00:00:00 UTC	2015-03-01 00:00:00 UTC	1	0	1
Mar 2015	2015-03-01 00:00:00 UTC	2015-04-01 00:00:00 UTC	1	1	0
Apr 2015	2015-04-01 00:00:00 UTC	2015-05-01 00:00:00 UTC	1	0	1
May 2015	2015-05-01 00:00:00 UTC	2015-06-01 00:00:00 UTC	0	0	0
Jun 2015	2015-06-01 00:00:00 UTC	2015-07-01 00:00:00 UTC	1	0	1
Jul 2015	2015-07-01 00:00:00 UTC	2015-08-01 00:00:00 UTC	0	0	0
Aug 2015	2015-08-01 00:00:00 UTC	2015-09-01 00:00:00 UTC	0	0	0
Sep 2015	2015-09-01 00:00:00 UTC	2015-10-01 00:00:00 UTC	0	0	0
Oct 2015	2015-10-01 00:00:00 UTC	2015-11-01 00:00:00 UTC	1	0	1
Nov 2015	2015-11-01 00:00:00 UTC	2015-12-01 00:00:00 UTC	0	0	0
Dec 2015	2015-12-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	1	0	1

What Hacker News says

3 sources

sebmarkbage·Jan 28, 2015

This is actually a way to eventually reduce the size of the library since it makes the class system optional. We're definitely considering optional module based systems instead of OOP, but it's still too early. https://github.com/reactjs/react-future/tree/master/07%20-%2...

In React v0.13.0 Beta 1

danabramov·Jan 28, 2015

It's funny React gets bashed in this thread for pushing out createClass crutch, mixins, autobinding into userland, when usually it is being modularity shamed[0]. The change is subtle and easy to misinterpret. It's not that React drank ES6 class kool-aid and we're now gonna use inheritance over composition. (Nope[1], in fact pretty much the opposite[2].) The real change is that React.createClass is no longer the way to create components. It's just a fancy wrapper (which is not even being deprecated). You want magic, you opt-in to it. ES6 classes are also not the way to create components. As mentioned at the end of the article, you can even use ES3 module pattern: function MyComponent(initialProps) { return { state: { value: initialProps.initialValue }, render: function() { return <span className={this.st

Read the rest

ate.value} /> } }; } React.createClass stops being special/required and becomes a (handy) utility. Can potentially be moved into a separate package. Competition for mixin systems is now possible. Finally, this change opens up more possibilities for potential React-like frameworks to “interpret” React components. Of course we don't do that today, but it's still a nice property and may be handy later when you decide to switch to future React-like competitor. It's the anti-lock-in. [0]: http://jlongster.com/Modularity [1]: https://github.com/facebook/react/issues/613#issuecomment-29... [2]: https://github.com/reactjs/react-future/blob/master/01%20-%2...

In React v0.13.0 Beta 1

insin·Jan 28, 2015

There's a mixin proposal in the react-future repo: https://github.com/reactjs/react-future/blob/master/01%20-%2...

In React v0.13.0 Beta 1