The Future of AngularJS

What <i>I</i> don&#x27;t understand is all the whining about posting slides.<p>This is fresh off the presses, answers hot questions in the angular community, and obviously people are upvoting it. If you&#x27;re aware of what&#x27;s happenning in Angular, every slide stands on its own and has useful info.<p>Can we please give all the moaning about format a rest please?

Neato. Angular reimplementing it&#x27;s own module system (when many developers already have a large body of code in existing module formats, particularly AMD) was one of the things that turned me off when first looking at it.<p>Do ES6 modules have all the dependency injection stuff the Angular developers wanted?

Unfortunately, I didn&#x27;t see improved documentation in their future vision...<p>I&#x27;m not sure how a lot of those ideas will work with compatibility with older versions of IE. You already have issues using the element tags for new attributes.

The Shadow DOM seems like beautiful for reading&#x2F;blocking output but I see most of my time with the &quot;Expand Shadow DOM&quot; option in the dev tools to see what the heck is actually going on during development.

Now whenever I see The Future of &lt;something&gt;, I asume such thing is getting killed.

I don&#x27;t understand why people link to raw slides. Are we meant to waste our time trying to read meaning from them like tea leaves?<p>Surely there is something to go with this slideshow?

I really cannot understand why this whole phase of &quot;posting my slides&quot; is becoming a big thing. Powerpoint presentations are useful in context. This link was of no use to me apart from some bullet points

You have to sign in with a Google account to access the content. All I get is a login page, at least.<p>Anyone got a link that is publicly accessible?

Being able to avoid $scope.$apply() will certainly be nice.<p>As it stands now, if you want to leave the Angular reservation and use something like the Parse JS SDK (which is a customized set of Backbone models) your code will be littered with $scope.$apply(). Not very DRY, and also adds, from the dev&#x27;s point of view, a needless level of nesting functions.

Do we have more clues as to what migrating an angularjs directive into a webcomponent will look like ?

What I want to know about the future of AngularJS is: what is the state of server side rendering? We have some of our own ideas as to how this could work at <a href="https://starthq.com" rel="nofollow">https:&#x2F;&#x2F;starthq.com</a> but I am hesitant to start implementing anything so as to avoid duplication of effort.

I was really excited when I saw the multiple responses possible for a given request

Personally, I liked that the slides are up there publicly, even if I don&#x27;t get to see the talk to go with them - they function nicely as a brief overview to the future of Angular, letting good devs fill in the rest. Much of this isn&#x27;t new, but I liked seeing some example code snippets comparing current and future syntax.

Is there a release schedule for ES6?

When ECMAScript 6 &quot;happens&quot; (any idea when that will be?), will we actually be able to use it or will we have to stick to old things due to browser compatibility?

does anyone know if there was a presentation that went along with these slides. it would be great to be able to see it. @briantford if you see this, we&#x27;d love to see more of the meat behind the bullet points. cool stuff though!

Am I the only one who thinks the name &quot;Angular JS&quot; is nonsensical and, frankly, a little silly?