Yeah sure, it's basically memoization applied to processes & distributed across the cloud

ah...finally, someone that gets it and says it aloud...if I would have found this comment before, I wouldn't have put mine further below. Thx!

Nowadays: want lots of traffic on your blog -> rant about Angular.

The problem is just that you're nearly a year too late.

- yep angular has flaws (which framework doesn't?)

- ya, it does dirty checking and yes, that might have perf implications if used the wrong way. But hey, 6 years ago when Angular was created it was a revolutionizing idea, and still holds today. Also, at that time no Objecte.observe existed, nor did SPAs really (well..GWT was kinda the solution at that time). But, did u check what they're doing in Angular 2? Heard about RxJS and stuff?

- DI: strange syntax techniques to work around minifiers? You don't really use those, do u? heard about ngAnnotate?

- Oh...AMD, UMD etc...do not dependency injection. And yes, agree, DI together in combination with AMD/UMD/... creates confusion with newbie frontend developers

- Then: Angular 2 is already live on GitHub, for a while; has even it's own webpage online

- and for god's sake..Angular 2 is compatible with Angular 1...read their blog posts, their Tweets, weekly meetup notes and design docs (all openely available on GDocs)

- oh..and there are even some rumors server-side rendering will be possible in ng 2

I like ur blog, but if you go and rant, please check the latest status, inform yourself, then rant. Nothing against critics, they foster discussion, but only if made properly.

Nice article! Just linked it in my recent post about getting started with ES2015: http://juristr.com/blog/2015/08/jump-start-es2015/

Thx

Nice, when I open one of the demo apps (http://foam-framework.github.io/foam/foam/apps/todo/Todo.htm...) on my mobile (Chrome beta), all I see is a small "f".

haha, that's what I thought as well...just that it isn't April 1st..

Interesting. I recently heard in a Podcast that Misko Hevery (a Googler) created Angular as his 20% project with the scope to make it easier for web designers to create dynamic prototypes.

He's the founder/author I was refering to.

It's not the first time I hear that he doesn't mention BRAT Tech LLC when he tells the story behind Angular.

The video is quite impressive, only for the call stack improvements you can get by using it. What's particularly cool is that it is framework agnostic.

So far I didn't use it, but will definitely try it out.

In fact, there's written "Visual Studio .Net 2003", so pretty outdated I'd say. There are no references about Lamda expressions, LINQ, dynamic support, async support and all the other awesomeness C# gives.

The "Visual Studio .NET 2003" refers to the version of the documentation. If there are different versions you can click on it to see them. Simply go up to the parent page -- you will see an example of this. If you go to the latest version of the parent page then there is no "C# Tutorials" link on it.

Which is to say, newer versions of these tutorials probably do not exist.

Yep, I played around a couple of hours yesterday and it is amazing how quickly you get up to speed (some basic NodeJS knowledge is obviously required). I'm trying to build some single-page app prototype, so I'll see how it performs once things get a little more complex.

But I generally like how it approaches policies, data store abstraction and seemless REST http and real-time socket routing. Awesome stuff.

Very nice additions.

However, I wonder how long it'll take till we can actively use them in production code...

That depends on you. From the article:

    Alternatively, many ES.next features can be experimented with using Google's
    Traceur transpiler (useful unit tests with examples here) and there are shims
    available for other features via projects such as ES6-Shim and Harmony
    Collections.'

There's also another quite comprehensive ES6 transpiler named six: https://github.com/matthewrobb/six

no it depends on browser vendors. Transpilers dont make generators or proxies magically works in ES5.

Same thing here, specially having to support IE all the time. :(

Same thing here :(

The compatibility table is here: http://kangax.github.com/es5-compat-table/es6/

Result: IE10 supports exactly zero of these features. We can start using them (maybe) once IE10 is dead.

Shhhhh Microsoft doesn't read the web.... they were completely unaware that ES6 was coming. The same way they were with HTML5 and much of CSS3. If only their employees were allowed to surf the net and see what cool stuff is being invented. Oh well, off to work on my cool ActiveX/VML Flash Shim....

Microsoft has a representative on TC39 (Luke Hoban) who is extremely active. In fact, I usually find that my thoughts on some new feature closely align with his.

Because Microsoft has bet on JavaScript heavily for Windows 8 apps (at least for now), and Windows 8 apps have full support for ES5, they have very good insights about ES5.

ES6 is still "coming". Many features are still in flux, and I don't blame Microsoft for not committing to in-flux ES6 features in the timeline of IE10.

I doubt we will ever get to use them, unless Windows 8 turns out to be such a clusterfuck that it takes Microsoft down with it.

IE9 still can't draw stroked text, for example.