Echo JS 0.11.0

It looks like there's definitely a push to get the async bits all in time... I think object rest/spread and object props are both pretty important in terms of cleanliness and usability.

It's been in stage1-2 for quite a while now.... Hoping this makes it in for EcmaScript 2017 cutoff.

And isn't it wild that 3 of these editors are based on Electron, which is OMG, JavaScript!

Nice find.. this could make an interesting option for a phone navigation app/server.

If you're targeting reusable components, then state should be left to the user of your component, or isolated internally via whatever mechanism you like, depending on the component.

That said, some will look better or worse over time, and component libraries will vary.  I mean there's Bootstrap, Semantic UI, Material UI and many other UI component libraries.  How well a given one fits into the react space, or even your own application will vary.  That's the nature of programming.

That said, in 20+ years of developing web applications, React is the first (of very many) web frameworks that felt like the right way to do components.  I'm not expecting that it will not eventually be replaced, only that of what I've seen lately, nothing is better enough to replace its' usage... though one might consider another JSX based implementation that's compatible (preact-compat).  I also remember many the libraries that were popular before jQuery came about (Prototype, mootools, etc).

If you don't have some form of state management, then you don't have an application... there are some abstractions that may work better than redux, such as the many graphql implementations that have been coming out.

While the use case may be a bit limited, I've had a few instances of loops and async promises where this would have been very useful...

LOL... not likely... tbh, React still feels like a better option than most next gen tools coming out that I've looked at.

Interesting, this is within striking distance of angular.js (angular 1.x), and over 3x where angular 2 is.

Nice article, I also use the term es7+ to refer to es7 + pending additions...   or es7+stage2 etc, since pretty much anything I care about is at least stage 2 now.  The latest being async iterables/generators.

I'm thinking of bumping the major on a few of my modules, and not transpiling for npm, just noting that the features are needed and noting that they should run via babel in any client usage...