Hello there,
This is a special issue of the AngularJS and Web Dev newsletter. In this issue I’ll be talking only AngularJS, only ng-conf 2015, and specifically about the things we now know about Angular 1.3, 1.4, 1.5, and 2.0 now that ng-conf 2015 is over.

Quick disclaimer: This is an extraction from the time I spent watching the referenced videos. There’s a good chance I misunderstood some parts or so.

Now, to the meat of it:

What’s happening in Angular 2.0


RIP AtScript .. Long live TypeScript

If you thought creating an entire new language to add an optional feature like annotations (attributes in C#), is, well, not the best idea, Google agrees!

So, they got Microsoft to sort TypeScript out, and are just going to use / recommend it.

Of course you’ll still be able to use plain ES6 or even ES5. But if you do, you’ll be writing some code that is redundant and the tooling / compilers can write for you. This is similar to how you can write reactJS without putting HTML in your JS (JSX syntax), except you write what the JSX-to-JS compiler writes, which is quite odd code to have to write yourself.

(for more about ES6, refer back to Issue8 of the newsletter)

Actually, mark my prediction, from a comment I made on an AngularJS facebook group yesterday:

TypeScript is “optionally” typed JavnaScript. They created it to be C# users friendly and 100% JavaScript compatible (any JS code is valid TS code). With Google cooperating, I can easily expect much of TS features to come in EcmaScript 8 or 9 (if too late for ES7).

New Website & Interoperability

There is a new Angular website dedicated to Angular 2.0, which is angular.io.

The site shows sample codes in JavaScript and Dart, but generally speaking, it’s still very early work in progress (there are references to AtScript in the docs still). I find it funny that the resources page happens to list only Savkin’s posts and the ToDo app video, which were all mentioned in the last issue of the newsletter, Issue9 :)

Having an entire new site reinforces how distinct Angular 2.0 will be. The team has an answer to your reasonable worry of this distinction:

The team will allow using Angular 1.x and 2.0 in the same application. You can have a parent Angular 1.x application with only parts of it using Angular 2.0, or you can convert your parent application to use Angular 2.0, and have each child application (not sure what this means, maybe child routes, given the new router supports both versions) still be 1.x and upgrade your child apps one by one.

The source code for Angular 2.0 is also available at github.com/angular. Don’t get this confused with github.com/angular.js (note the .js suffix), which is where Angular 1.x lives now.

What To Expect

The general themes that the team is focusing on in Angular 2 are:

  • Simplicity

    They are hoping the new component classes (directive replacements) and HTML templating syntax will be easier and make much more sense than existing ones.

  • Speed

    One way data binding (instead of 2-way data binding, which has implications on forms directives changing a bit) and changing the way scopes work -now called zones, and don’t requite $digest or $apply pain or having a special name- among other internal changes are reducing memory and DOM writes, causing possible 10x speed increases.

  • Consistency

    The new syntax Angular introduced for using directives in templates in Angular 2 aims at solving consistency problems we have in Angular 1. Examples from my understanding:

    Currently in Angular 1.x, with attribute directives, the directive author decides whether to use JavaScript expressions as the value of the attribute/property, or just a plain string property. I for one know that I always forget that to use ng-include I must put the template name inside quotes like 'template.html' because it takes a JS expression not a literal string (which is good).

    As a directive author as well, I also hated that I need to do extra work to support {{...}} syntax in attribute value. As both creator and consumer, I hated that each event I need to capture needs to have a directive (ng-clickng-blur, custom directive, etc, and yes there are workarounds).

    It’s even hard to tell whether a directive is meant to be a template that replaces the element completely or just adds an event handler or some properties. Some of you probably had problems when they accidentally tried to use two directives when both use the transclude feature.

    Solving these problems is at the heart of Angular 2, by giving a unified syntax for choosing whether to pass a literal string or JS expression when using a directive, and providing unified syntax for handling events without even needing to write a directive for that, also providing different syntax for template directives than component directives (which don’t rewrite the element).

    This bit can be quite confusing to explain in words. Check Day 2 keynote (linked below) for more about what the new syntax looks now, and why – Highly recommended.

  • Web Components

    To explain this without assuming knowledge of what Web Components are, I’ll use some over-simplified definitions (so, don’t make that offend you if know about Web Components). For a more proper introduction, check my video [Introducing Web Components & Polymer Projectpolymer-video, or the resources I used to learn about it, mostly listed in Issue7.

    Angular 2 embraces Web Components in two ways: first, it uses the Shadow DOM for template components (think: template/transclude directives).

    Shadow DOM is like inner HTML that is not affected by any CSS styles (even browser styles), cannot be matched by normal CSS selectors, and has its own child DOM document. Think of the many elements that browser renders when you add a <video tag to the page. This is the usual Shadow DOM example, except here we are talking about Shadow DOM that you create, style and control, not the browser.

    Shadow DOM is great for building reusable components that are guaranteed to not conflict with anything else on the whatever page they get used in, although can be a nightmare to style using today’s common CSS techniques that rely heavily on CSS inheritance / cascading. I hope that Shadow DOM will be optional, but I’m not sure.

    The other way Angular 2 embraces Web Components ensuing that Angular components (directives) can be used with / within Web Components transparently. You should be able to use custom HTML elements that have their own templates and Shadow DOM with Angular just like you’d with native HTML.

    This is the reason for all the weird [] and () characters used in directive attributes in Angular 2, so that they can be passed through the new HTML <template> element, often used in custom HTML elements (~ AKA Web Components) without being processed by the <template> itself.

    One thing to mention here: Google has another framework for building applications using custom elements / Web Components, Polymer Project. It enhances the new built in HTML <template> element and APIs to create custom elements and shadow DOM.

    In the Q & A session the Angular team explicitly said Angular 2 & Polymer are meant to work together very well, but are NOT likely to be merged in the future.

The first migration to Angular 2.0 will happen internally at Google around May 2015 (sounds too early to me, we’ll see).

This is all coming from the Day 1 keynote session (keynote-videoslides).

Whether you check Day 1 keynote or not, I highly recommend that you check Day 2 keynote.

It covers a lot about what the new Angular 2 syntax looks like (for both HTML and JS), and the reasoning behind it. It’s a true crash course (keynote2-videoslidesdemo code).

From Q & A

In addition to above, here are the bits relevant to Angular 2.0 from the Q & A session:

  • The current plan is to make Angular 1.x and 2.0 work together and work side by side, even with either of them in the module / app containing the other. By embracing this direction, this seems to leave out providing a proper compatibility layer in place (although it might happen, as I’ll show below).

  • Angular 2 will support evergreen (auto-updating) browsers on the desktop. This means IE 11+ (this can obviously be a deal breaker). Mobile support matrix is not decided yet.

  • The template language in Angular 2 will probably be a MUCH better experience for directive / component creators. You think it’s crazy to create your own ng-repeat-like directive in Angular 1 (maybe you don’t even know what interpolation means)? Even this sort of stuff should be easy in Angular 2.

  • Serverside rendering in Angular 2.0 is not a no-no as we used to hear before. It’s not promised as well. The team think that the changes they are implementing in Angular 2 will have positive side-effects on server-rendering story, but it’s obviously not something they are actively working on enabling.

    To me this sounds like it might be easy for a 3rd party to build it, or may come in future 2.x releases past 2.0.

  • There was no mention of Angular 2 filter feature in previous sessions as in pipe filters, but that will still be supported, probably renamed to pipes (as in stream passing I guess, like gulp, etc. in node). The team promised this will be such a lovable improvement.

  • As Angular 2.0 will be written in TypeScript, Angular will use the Traceur compiler to translate TypeScript output to EcmaScript 6, EcmaScript 5, and Dart. This allowed Angular to merge the AngularJS and AngularDart teams into one.

  • This one is crazy and hard to explain if you don’t know C#, TypeScript is on road to have something like async/await syntax, coming from C#, this syntax allows you to write asynchronous code without any big changes to your existing code. And guess what? The team suggested that this feature is already used in the codebase for the new Angular router – somehow (haven’t checked code yet).

    My poor attempt to explain the feature: imagine you can add the word await before any method call that returns a promise, and after that, instead of having to call .then() and pass a function, the compiler assumes the rest of your code (within the current function) IS the then function.

What’s happening in Angular 1.x (Angular 1.3, Angular 1.4, and Angular 1.5+)

It looked like Angular team felt that they needed to show proof that they have good reasons to not screw Angular 1.x users, so here’s what they said:

There are 2,000 apps using various versions of Angular 1.x at Google, and ~ 1,000,000 users (1 million!) visiting the current angularjs.org website (fully dedicated to 1.x). There are also 400,000 monthly visitors to the actual Angular 1.x github repository. The team showed that they get how big and dead serious Angular 1.x user base is.

By the way, it was also mentioned that Twitter uses Angular 1.x for several internal systems, and PayPal has a new checkout experiment using AngularJS 1.x as well. That’s an app that generates REAL MONEY!

What To Expect

The themes that the team suggest they’ll spend effort on with Angular 1.x are:

  • The new router
  • Internationalization / localization
  • Material Design (directives that implement Google’s Material Design)
  • Changes that can make it easier to migrate to Angular 2.0
  • General support for any issues / bugs etc.

This shows currently in the following efforts:

  • Weekly batch (1.x.x) releases (bug fixes, backwards compatible features)

    There are fourteen 1.3.x releases at the moment. Turns out the target is weekly releases!

    This is exhausting to keep up with. You might consider a 2 or 4 weeks update in your apps. But the idea is that breaking changes are minimal in these releases, and the bigger breaking changes are saved for 1.x releases, like 1.4, 1.5 etc.

  • 1.4 RC0 is coming out this week

    If you followed the previous issues of the newsletter, many expected a final version of 1.4 in ng-conf. This didn’t happen, which is OK.

    The scope for Angular 1.4 as planned in January was a bit small IMHO. They added a few more things (so, it’s still not a big ball of mud update), and pushed the date slightly.

    I’m happier this way, because I thought we’d hold our breathe for for things like the router till 1.5, which would take even longer to come (it’s still likely major improvements will happen by the time of Angular 1.5).

  • Angular Router is coming to Angular 1.4

    The initial release of the new official router, which combines features that used to exist in ui-router (like nested routes) will come as part of Angular 1.4 announcement.

    It’s still going to be a separate library though. It’s supposed to work with Angular 1.x and 2.0. And it will have its own release cycles independent from Angular 1.x/2.x releases.

    This is also great. I’m hoping the initial release will be good enough to recommend it instead of ui-router, because the new router is eventually what most apps will end up using in the future anyway.

  • Localization / Internationalization in Angular 1.4

    I don’t know much about what is improving, but I know that the internationalization library for AngularJS is Angular-Translate, which is a very good looking one from its site or the ng-conf session about it (translate-videoslides).

  • Performance Improvements

    The team always manages to find areas to improve internally on $scopedigest cycling, ng-repeat etc., that quite often getting a new Angular release will give you a performance improvement with no code changes.

  • Continuing to plan in public

    That probably refers to publishing their weekly meeting notes on Google Drive (and sometimes recording them, although this is less often), as well as the usual OSS openness, that is: planning via public Github issues, accepting pull requests and responding to comments on Github issues and commits.

  • Shared components between Angular 1.x and Angular 2

    The components announced to be shared are:

    • the router (of course)
    • Internationalization support
    • Animation support (this is a bit of a surprise to me)

    Note that Material Design is not in the list, which makes sense because it’s quite more involved (it’s all about writing directives that apply the Material Design). Maybe that’d be a good migration / compatibility test subject, Google -if anyone is reading this :)

    A lot of this will be in proper shape by the time of Angular 1.5 (with some bits coming in Angular 1.4). Angular 1.5 could be happening around Summer-Fall (U.S. calendar not Aussie calendar of course).

Most of this came from Day 1 keynote linked to before, and from the Angular 1.x session (ng1-videoslides).

Getting your Angular 1.3/1.4 App Ready for Angular 2

Here’s what the team says about preparing code for less migration effort when we get Angular 2.0, which is luckily in-line with the guesses that several others came up with so far.

  • Write code as ES6 classes, everything (directives, services, etc.)
  • Use the new Angular router (luckily it’s just around the corner)
  • Use directives more than controllers
  • Use the controllerAs syntax in your directives instead of using $scope

There already is a proposal for a compatibility layer to be introduced. You can see some actual code by watching the “Angular 1.3 meets Angular 2 0″ session (ng13_20-videoslides).

From Q & A

Here are a few bits from the Q&A, that are supposed to happen as part of Angular 1.x development story / ecosystem:

  • It seems the Angular router team, at least those present at ng-conf, don’t know much about what ui-router provides. This is weird, but maybe because the Ember router is where they are getting most of their inspiration from.

  • The ng-inspector Chrome extension might be merged with the Angular Batarang extension going forward, if the conversations start soon and go smoothly

  • Angular Material Design animation support will come to Angular 1.x, but beyond 1.5.

    Google Material Design (a lame yet easy way to think of it is like Twitter Bootstrap & Windows Metro design mixed into one) defines UI look & feel, and some standard animation effects even on things like pressing a button.

    Angular Material Design 1.0 will come around Angular 1.5. It’ll have all UI styles builtin so that just adding ng-button or something like that will get you a Material button.

    However, the animation part of things will follow later with a new feature coming to Angular Animation library called “timeline”. This is required as Material Design animations are sometimes series of animations not a single animation effect.

And of course, the Q & A session is also available to watch (watch).

These notes do not cover entire ng-conf

You can watch all the sessions from ng-conf on the ng-conf 2015 video playlist.

There are sessions about the new router, TypeScript, reactJS, a performance benchmarking tool called benchpress (used to measure performance improvements in Angular 2), John Papa’s AngularJS styleguide, and much much more…


As you watch the videos, you’ll find most presents link to their slides near the end or so. I have linked to all the slides I could find whenever I linked to a video.

If you didn’t find a slides link in the video, here’s what I did to get the “Angular 1.3 meets 2.0″ slides: I went to ng-conf schedule page, found the talk details, clicked through to the speaker’s twitter account, and asked for the slides gently :)

I’m sure there’ll be some list of slides (official or not) at some point. I’ll keep you updated via this newsletter when I find about it.


Here’s a big list of all ng-conf videos, slides, and speaker twitter links.


If you liked this special issue of my AngularJS And Web Dev Goodies newsletter, please let your friends know about it and sign up as well.

Thank you!


Eng.Meligy@Gmail.com | twitter.com/meligy | gurustop.net/newsletter


@Meligy's Newsletter ng-book Giveaway

Hello there,
This is a quick newsletter this time, just to give you something before ng-conf. No one knows how the next one will be influenced by it.

I will be spending several hours watching videos and stuff to see highlights for next issue.

For now, let’s see what we have…



ng-conf Submissions

ng-conf used an interesting way to choose speakers and sessions. They set up a Github repository and speakers went ahead and created issues and pull requests for their submissions.

This newsletter is a good place for exclusives and semi-secrets. I have been following this Github repository for a while for inspiration of what topics to talk / write about for AngularJS.

There are many topics that maybe are not fit for for ng-conf agenda, but can be good topics for a blog post, a YouTube video, a small book, a Udemy or Pluralsight course, etc.

ng-conf Schedule

For the really lazy, plus it’s surprising how much content there is going to be there. I was like “WHAAAT? ALL OF THAT?”…

Angular 2.0

Victor Savkin’s blog

Victor is a member of the Angular team (although he used to work on Angular Dart). He started blogging about Angular 2.0 and already has some interesting posts to check out:

He also goes into interesting areas, like building Angular applications using the Flux architecture (that’s the architecture that is recommended for reactJS development).

Video: Angular 2 Preparation – Part 1 – Code Structure Comparison

A video by a guy who is also a speaker at ng-conf. He is hilarious, overly too hillarious that it doesn’t really match my taste, but his Angular 2. video has a interesting hihglight: actually looking up the public Github repositories for checking what Angular 2.0 doesn’t need you to be a JS guru or so.

The highlight is from the dependency injection bit in the video. If you have 7 minutes to waste, it’s not that bad :P (or else wouldn’t have added it here).

What’s New in AngularJS 2.0

OK, about this one, here’s the thing. It’s not the best place to get a sense of what Angular 2.0 code is going to look like. You are better off with videos and blog posts in various earlier issues of this newsletter like the todo one from Issue 8

BUT .. It’s a good listing of all the feature areas in Angular 2.0. So, if you are after a comprehensive list of features and highlights, this is a really good one.

Angular 1.x

$ngCookies to support passing path & domain

It only took 2 years and 2 months, but AngularJS is finally getting a built-in cookie provider that’s actually useful! I talked about other alternatives in Issue 7 of the newsletter.

The commit is in master branch, used for Angular 1.4. I don’t see it in changelog for 1.4 beta 5 yet. It should be in the next release (whether it will be beta or not) likely to be announced in ng-conf.

Ionic Framework

Ionic is a framework that uses AngularJS and Phonegap to build HTML-based mobile applications. It provides great tooling for performance and mobile-focused UI, etc. It’s pretty much the go-to framework for mobile development with AngularJS.

Mastering the Ionic Framework Tutorial

A good step-by-step tutorial for learning Ionic for those who haven’t tried it before. It is a good written tutorial (it also offers a video version you can check if you want more guided version).


Passing Data to Angular from ASP​.NET MVC Views

There is a single idea to take from here. You can have the data ready from your controller in the same page and just pass it to Angular. You don’t have to have another service if the data can be known at the time of the page load already. Later interactions can still depend on other REST services.

I have used similar approach in many AngularJS apps that I developed (where Angular was used for reach UI rather than single-page app), and it was always very useful.

Love & Hate

Is AngularJS ready for the enterprise?

I wasn’t sure whether I should include this in the newsletter. I mean .. really .. we don’t need more “Is Angular relevant?” questions, but the article itself isn’t too bad, and might make a good snack read or skim or whatever.

HTML5 & Web Components

Web Components is a term that refers to several new HTML non-finalized standards that add allow things like built-in template language, and completely independent pieces of HTML (shadow DOM) and more. I talked about it earlier in Issue 7 in a section with the same name as this section.

Video: Introduction To Web Components And Polymer Project

This is an introductory session (40 minutes) I gave this year about Web Components in general, and about Polymer, a Google project that builds on top of the standards and provide a great framework to build independent widgets with them with data-binding and more.


ASP​.NET 5 (vNext)

Top 10 Changes in ASP​.NET 5 and MVC 6

A very good summary on what to expect just to get a sense of how things are changing in Microsoft space.

There’s also another very good summary from Microsoft’s VP who created the first version of ASP​.NET MVC framework, Introducing ASP​.NET 5.

Understanding .NET 2015

The previous pick was a summary with code samples, specific to ASP​.NET. This one is the whole big picture with all different bits.

For example, you might have heard about the new compiler, Roslyn, do you know htat there other 2 new compiler shipping in the next version of .NET? Are you sure you really know what the new .NET Core thing is? This article answers those kinds of questions pretty well.

(And I realize this last paragraph sounded like a link-bait, yuk! – Sorry!)

Domain Driven Design (DDD)

Why do all my DDD apps look the same? – Slides & Video

This one seems to be an interesting take on how DDD sometimes goes wrong when you try to do it right. I have checked the slides -pretty inspiring- and the video is on my list (maybe not soon with ng-conf here).

I personally silly they require you to sign up for the video now. If my memory didn’t fail me this is a relatively new requirement. I have watched a lot of Skills Matter videos before and it’s usually very good (and often advanced) content though.

Developer Tools / Editors / IDEs

Visual Studio

– Using jspm with Visual Studio 2015 and ASP.NET 5

JSPM is a package manager for SystemJS. SystemJS identifies itself as “Universal dynamic module loader – loads ES6 modules, AMD, CommonJS and global scripts in the browser and NodeJS”. Why you might hear about such a thing?

Well, SPA frameworks of course, and ES 6. I talked about Aurelia in Issue 8, and if you watched the video, the author of the framework really likes SystemJS.

It also seems Angular 2.0 although will not embrace it officially (I guess), the push it will make to writing code in ES6 will raise the need for a framework that can play well with existing package styles and ES6 modules.

So, it’s a bit futuristic. Visual Studio 2015 is not final yet, but if you want a peak of more likely future trends, give that post a quick skim.

Sublime Text

– Themr & Schemr

If you use Sublime Text, and you get bored as quick as I do, you probably also change themes and colour schemes quite often. Those 2 Sublime Text plugins make the perience much easier by allowing to visually switch between themes and between colour schemes, with preview and very nice UI.

You can find Sublime Text themes everywhere. Here’s one list I found last week.


I read that quote and thought, this is exactly the message I want to tell all of you, ladies and gentleman:

reminder– you might feel like you’re imposing by asking someone if they’ll mentor you but more likely you’re making them feel honored (source)

I’m happy to help you with any issue you have related to ASP​.NET, AngularJS, or JavaScript. Just email me / reach out.

Apart from that. I’m still making small changes to the newsletter in every issue, and hoping to get feedback from you whether it’s going where you’d like to continue going. I’ll be back after ng-conf, not sure with what yet.

Stay tuned, and yes, please let your friends know about the newsletter.

See you,

Earlier this year I talked to ALT.NET Sydney about the new big thing after HTML 5, yes, Web Components. I also talked about how you can create and consume Web components using the Polymer framework.

You can watch the talk from here:


Hey maties!
It’s been a while since last issue, but it’s my birthday today. What could be a better execuse to take a day off from work, sit in a nice cafe, and compile some of the drafts I have into a new issue!

I originally had a longer opening, talking about how this list has grown to include over 290 real people, and how one of my goals is to reach 1,000 before next year. I planned to ask for help spreading the word.

But we are over this now already, aren’t we? Let’s keep it short and get into content.


Angular 2.0

An Angular2 Todo App: First look at App Development in Angular2

Before this video, everything most people knew about AngularJS 2.0 dated back to the teasers in ng-Europe last October. People had to go through Github commits and issues or meeting/design documents (which are publicly available and I linked to some earlier in this newsletter) even just to get a feel of what is going on.

The video (from a usergroup meetup) has a code demo, which shows the new HTML templates as well as the directive (or component) definition syntax, with the C#-attribute like AtScript sugar.

It also has a good Q & A session on the progress, and how it relates to other areas like, obviously, Angular 1.x, and how Angular 2.0 will remove 2-way data-binding!!

ng-conf 2015 | The AngularJS Conference

The next Angular conference is already around the corner, coming March 5-6. Keep an open eye on it!

I intended to put this in here because I was like “Sure there will be Angular 2.0 stuff in there”, even though the schedule only mentions it in a single talk!

It’s also mentioned in the above video that the team has more to say about it in ng-conf.

Note that Angular 1.4 will be announced in ng-conf as well. That’s already in beta 4 stage (as 1.3.x is now at 1.3.13). If you follow the newsletter for long, you know the best place to keep up to date with versions, the changelog.


Karma and Mocha for AngularJS testing

If you are like me, you are probably tired of so many names that come to mnind around testing, especially when it comes to AngularJS. This post helps a bit.

It picks a chain of tools, tells you what the choices it made are and what they do, and help wire them all into a usable workflow.

Visual Regression Testing For Angular Applications

Implementing responside design involves a whole lot of CSS breakpoints and JavaScript interactions etc. With all that going in the page, it can be quite hard to test these interactions beyond testing in so many devices.

The article presents a relatively simple approach that you can use on the long run to make sure new UI components are not breaking the existing UI. The approach feels useful even beyond responsive design, although I haven’t played with it (yet).


Unobfuscated: Angular.js Accessibility

Nice collection of blog posts about accessibility when using AngularJS (read the old ones first). Also has good work around improving the accessibility aspects of the TodoMVC sample AngularJS app.


Yes, Microsoft has found that React‘s popularity is not to be missed, and similar to catching up with Gulp support in soon-to-be-released Visual Studio 2015, they decided to support reactJS as well.


Aurelia is new JavaScript framework similar to AngularJS, EmberJS, and DurandalJS. Actually, it replaces DurandalJS, as it is from the same author.

Introducing Aurelia
Remember Rob Eisenberg, the guy behind DurandalJS? He joined AngularJS team working on the new pre-release Angular 1.x/2.0 router, he wrote the “All about Angular 2.0″ post, then he left the team hinting to go work on Durandal NextGen.

Just in case you missed hte news last month. It seems he created yet another framework instead, Aurelia. In this post there’s a video that shows so many similarities with what Angular 2.0 is supposedly going to look like, except his bits are actually available for using today, and he doesn’t go too far to create something like AtScript.

The framework is really interesting, and people -of course- have already started writing about ditching Angular for Aurelia, as usual with every other new framework out there ;)



The new version of Javascript, which introduces interesting features features like classes anad modules, and scope variables (vs. function-level variables).

It’s not yet supported in most browsers, but there are tools to translate it to Ecmascript 5, the currently supported JS we know.

Getting Started with ES6 – Transpiling ES6 to ES5

A very simple tutorial on using 6To5 and gulp task runner to start writing code in ES6 today and translate it to ES5 for browsers. I here link to the entire (tiny) ES6 category in the blog for more about ES6.

Dan also has a nice Github repository of samples he links to in the post, which is very helpful for getting to know the new ES6 feature.

Dan Wahlin is a popular video course author and more, and the guy who made ths Angular in 60-ish minutes video I always recommend to devs new to AngularJS.

ES6 Language Specification Draft from Mozilla

Yes, it’s true. ES6 is not final yet, although most of it is pretty stable, so it’s not something to be worried about.

Learning a language by reading its specification is a very interesting way, and (sometimes) is not that crazy. This is the PDF standard rendered as HTML instead of PDF, with links to the official PDF and Word documents.

Give it a look (note that this is the entire language specification, not just what’s new in v6).


ASP​.NET 5 Updates and other improvements for Web Developers in VS 2015 CTP 6

Visual Studio 2015 CTP 6 came out yesterday. There’s a great official announcement, and the release page shows a (very) good summary of new features in all areas, but this link above is the detailed coverage of what’s new in ASP​.NET 5 (also known as ASP​.NET vNext).

General Web Dev

Some of you remember I made this list to remember the cool links I neeed ot check or come back to. These up are a few!


HTTP/2, the first major change to HTTP in 16 years, has been finalized

It will take a while to be the norm of course, but HTTP 2 can be a real big deal. It promises a lot of speed enhancements, and one interesting enhancement is being able make multiple resource requests in one go. This alone can be very inspiring.

Let’s wait (quite a bit) and see what comes out of this. Again, it should be big!

– HTTP2 Book – Mozilla (PDF)

If you really want to dig into the protocol, this is a good read. It’s by a Mozilla guy who works on the protocol itself.

And it’s not even a specification (so don’t freak out), it started off a presentation he delivered last year. Check it out, it shouldn’t be too bad ;)

[Issue Bonus] Free Web Development Videos

Level Up Tutorials

I’m very surprised this site is not popular. It’s like egghead.io, a big library of free videos with some premium content. Except the videos cover a really wide range of topics.

It had a series about Web Components & Polymer Project that I found very useful for getting up to speed with it, but it also very wide range of topics like: SASS, CoffeeScript, Grunt, Gulp, WordPress and other topics, like Android dev and basic Mac command line.

Toptal Videos (AngularJS, JavaScript, UnderscoreJS)

This is a freelancing company that tries to market itself as a place for top developers. I don’t know who they are but I’m also not in the market for that need anyway. What I know is that they have very good articles and videos.

One thing I wish they did was provide some sort of tagging or categorization. I saw their AngularJS stuff and was nice. They also have some JS & UnderscoreJS-specific stuff. Should be worth skimming the list.

Microsoft Virtual Academy
Not many people know that Microsoft have some great online courses on C#, Mobile Development, BI and even the prerelease ASP.NET 5. Yes, another unpopular gem!

Not really something that would “teach” you, but think about it. live coding sessions streamed + recorded, on Reddit. Could it get any better?! Could it get any worse?!

In closing…

Send me good resources, please!

You probably didn’t know that Toptal contacted me explicitly last month to include their videos in the newsletter. No affiliation of any kind was there.

I didn’t get anything directly or indirectly from linking to them. I just checked their videos, loved them, and decided that I should have found them on my own earlier! So, I included them in this issue.

If you find any good links (created by others or even by yourself), just email me.

I’ll check them out, and if I find them good for me, they’ll hopefully be useful for other readers of this newsletter as well. So, I’ll include them, and (unless you tell me not to) thank you for sharing awesomeness.

Spread the word, Please, please, PLEASE!

If you did like this newsletter, there are a few things you can show the love. Having an idea that can make even more awesome and emailing it to me is one thing I can’t thank you enough for (same for things that could make it suck less).

Another way to show love is to tell just one friend or colleague about it. Maybe in person, in email, on twitter, or whatever really. The more people reading this, the more responsible I feel about NOT making it suck.

Thank you!


Eng.Meligy@Gmail.com | twitter.com/meligy | gurustop.net/newsletter

, , ,