Echo JS 0.11.0

That's your personal experience and personal experience depends on person and project. I had more than 3 months to work with pretty big ng1 codebase and I'm still unable to wrap my head around all these "@", ">", "=" and all ng1 cryptic syntax for property-binding.
At the same time I dived into ng2 easily (with prior RxJS and TS experience, though) w/o any guidance. Much easier than e.g. Ember.
Of course, ReactJS was even easier than ng2, but for any big app you'll need redux, redux-thunk, redux-middleware and all other bells and whistles, which makes actually learning ReactJS.
And after several years, saying I program in React will not mean anything, because do you use flux-saga (not a real thing, probably) or redux-thunk? And with Angular2+ there will be only one type.
Ng2 might never reach popularity of React, but it will have its niche in Enterprise world.

Pretty captain obvious-y article. Learn vanilla js & react or angular 2.

https://github.com/systemjs/systemjs

Exact quote:
Built to the format ES6-specified loader API from [ES6 Specification Draft Rev 27, Section 15](1), and will be updated to the [WhatWG loader API](2) as soon as it can be considered stable for implementation.

[1] http://wiki.ecmascript.org/doku.php?id=harmony:specification_drafts#august_24_2014_draft_rev_27
[2] https://whatwg.github.io/loader/


Just in case: Yes, this is *draft*. But the point in article is the following: "We need to learn something new, which is specific to Angular and isn't used elsewhere" and that's plain wrong.

Mostly whines from a person who worked with angular 2 for 2 weeks and doesn't even know that SystemJS is the STANDARD way to load js.

80% of described there is the same for all C-like languages and 100% of it (and much more) is on MDN [1]

[1] https://developer.mozilla.org/

I'm front-end guy and I'm missing the problem with that article. Arguments in article seem reasonable, what's wrong then? Does he generalise one example of bad middleware code to all middleware or is that code even okay and he misses on the idea of middleware?

Are there enough hooks for state serialization for those obsessed with data compression?

I don't think Oracle by itself is a problem, but the article says nothing why we should use that technology, hiding a link to the site deep in the article.
So according to Oracle's site it's just another Universal Toolkit for web & hybrid mobile.

And the problem is... they're late for this game. While technology might be OK, it will never enjoy decent adoption by community.

It suits only very straightforward pipeline.

[async functions](https://github.com/tc39/proposals/blob/master/finished-proposals.md) are already stage 4.
Who needs a[n alternative syntax] Functor when there's a Monad already?

It's viable to implement dynamic part in CSS, something along these lines:
.star + .star:hover { color: #ff6d00; }