Echo JS 0.11.0

Doesn't this also make tree-shaking basicly impossible? Since the tree-shaking tool can't just strip code away because it doesn't know if that code was importet somewhere via dynamic import().

Does "functional representation all the way down" mean that you never inherit from Component in the React apps you are building?
I've found the Functional component lifecycle events Inferno has quite interesting ( https://github.com/infernojs/inferno#functional-component-lifeycle-events ). Hopefully React will implement a similar feature some day (now that they hired the Inferno guy :) ).

Although I'm using JSX myself, I think it obscures what is happening under the hood. I don't really see what advantage it has over something like Hyperscript, besides looking a bit similar to HTML. There is an interesting Blog Post from Andre Staltz regarding JSX: http://staltz.com/some-problems-with-react-redux.html

nice job!

Can you point out some benchmarks? Would be interesting.

However, if you have performance issues in your app there are probably a lot of things you can optimize, before replacing the promise library. I never worked on an app where the performance of promises became an issue.

I disagree. IMHO you shouldn't pull in a huge library like bluebird just to run promises in a sequence. That is like using jQuery just because of $.ajax.

Btw Sindre has also released a bunch of small promise modules recently: https://github.com/sindresorhus/promise-fun
Worth checking out.

The nice thing about vuejs is, that you can also just define a render method and use JSX. So you don't have to use template strings.

https://vuejs.org/guide/render-function.html

I had a deeper look at vuejs a few weeks back and I really enjoyed it.

It's like the best parts of React, MobX and Angular have been mixed together, surrounded by a nice, clean and simplistic API.

Maybe Promises are just the wrong tool for this kind of stuff in general. 

Interestingly it would be no problem solving these problems with Observables. Cancelation can be done with `dispose` and  setInterval would also be trivial to implement.

I agree on that. In about 30% of the cases, that I use setTimeout, there is some cancelation logic involved (polling, debounce etc.).

It depends on what you are doing:

If you are coding some app type of thing, you probably won't need it anymore.

If you are building a typical wordpress website, with sliders, lightboxes and a bit of form validation then it's still handy to throw jQuery plus some plugins at the problem.