robwormald

Ugh. Thanks for the kind words :)

I did the Mars demo at a conference a while back - the first couple of minutes I was underwhelmed, but at some point, my brain "bought-in" - I noticed this when I crouched down to look under a virtual rock outcropping without a second thought.

You'll be pleased to know that we're making Zones optional pretty soon here. This would mean taking control of change detection yourself, of course, but there's plenty of valid use cases where that's a reasonable idea.

FWIW, Angular's release cycle is roughly based on the same cadence as React :)

Angular core team here, we're restructuring some of our docs at the moment and this is super useful feedback. Thanks!

It's unlikely we'll ever have developers write Custom Elements directly - that said, the View Engine rewrite we just did gives us the ability to (theoretically) have our compiler output Custom Elements. We're investigating some use cases on this.

This is what the AngularJS versioning scheme was, nearly exactly. Everybody hated it. Hence, semver :)

1) the core of Angular Universal "graduated" into @angular/platform-server with 4.0 - previously it was a more experimental project. We're officially supporting a "renderToString()" API that can be used however you like.

So really, it's brand new, and we're excited to see what the community does with it.

Philosophically, pre-rendering every SPA server side isn't a silver bullet. For a ton of cases it makes a lot of sense, but we want to avoid the impression that we're positioning SSR as a replacement for making your app fast.

2) The expectation of the Material Components Web project is that everything be "wrapped" for the specific framework. Angular Material is native Angular, and we have a team dedicated to that. Polymer has a material suite as well, and most of those components can work in Angular apps too. Components for everyone!

2a) you're asking a Googler that question. We have like, 11 messaging apps. I don't know what to tell you.

3) CLI went stable today, with its 1.0 release. We'll be moving the docs over to use the CLI everywhere soon - personally, i'd use the CLI to generate a new project and then follow along the tutorials.

absolutely. we're 100% invested in Rx, and more than anything else I'd like to see the Observable type standardized.

You can already use most simple web components in Angular without issues - as far as Angular is concerned, it's just another DOM element.

We also support native (or emulated) Shadow DOM out of the box.

It gets a little more interesting when you start interleaving Angular and WebComponents, but one of the deprecations in 4.0 (regarding Angular's use of the <template> tag) is squarely aimed at making that easier in the future.

This is good to know, cheers!