I might take a look at this, have not yet looked into Angular.
It is a little disappointing to disable javascript and refresh the page at www.learn-angular.org, it's just a blank page. As much as I'm a javascript fan, and have made single page apps, a completely blank page without JS just feels wrong. I'm guessing this isn't the fault of Angular.. or is it?
While Angular can certainly be used for simple progressive enhancement-kind interactions, its strength lies in single page/fat client apps, and in this case not having javascript and still getting basic functionality would mean duplicating it on the server. Still, it would be a good idea to display a noscript message alerting the user about the JS requirement.
Looks promising, but the videos don't seem to buffer for me at least. My internet isn't strong enough to play it continuously so I normally just pause videos, wait a few minutes, then try playing them. Doesn't seem to make a difference with their videos for some reason. Any tips?
They're probably using DASH[1].
The video is split into several segments and therefore the player will fill the bufer only until the end of the current segment.
Below each codeschool video you have a download link, so you can view them offline.
I went through these yesterday, they are some the best tutorials out there right now for Angular IMO, I recommend anyone wanting to learn Angular to check them out.
Great tutorial. I love these interactive lessons, but one thing I'd love to see in this tutorial (and many others like it) is something that Michael Hartl does in railstutorial.org, which is an extra credit section.
In the later sections of the tutorial, the addition of some suggestions for extending each example would be great. You don't need any "stuck" functionality or anything like that here; just some casual examples of how else you could use the subject of the tutorial would really help solidify the concepts.
Seeing how I figured out how to index angularjs pages for searching myself in one evening I imagine it won't be too long before google improves on this.
Or rather - even if Google figures out how to index these pages, why should every other consumer of web content have to also figure it out when it's the fault of the content itself.
I would tend to agree that google needs to solve this problem for indexing. They were the source for angular.js and they must realize that stuff they want to index will be buried in one page javascript apps going forward.
Awesome resource and great lessons. I just went through a lot of them, but I have to say the quality of the new CodeSchool course is amazing (and a lot more comprehensive than this one).
26 comments
[ 28.9 ms ] story [ 1006 ms ] threadIt is a little disappointing to disable javascript and refresh the page at www.learn-angular.org, it's just a blank page. As much as I'm a javascript fan, and have made single page apps, a completely blank page without JS just feels wrong. I'm guessing this isn't the fault of Angular.. or is it?
http://campus.codeschool.com/courses/shaping-up-with-angular...
The more the merrier!
Below each codeschool video you have a download link, so you can view them offline.
[1]: http://en.wikipedia.org/wiki/Dynamic_Adaptive_Streaming_over...
http://play.golang.org/
But also in their tutorials:
http://tour.golang.org/#1
In the later sections of the tutorial, the addition of some suggestions for extending each example would be great. You don't need any "stuck" functionality or anything like that here; just some casual examples of how else you could use the subject of the tutorial would really help solidify the concepts.
Now look at the source with ctrl+u. (example url: view-source:http://www.learn-angular.org/#!/lessons/binding-css-classes)
Now you know why he needs server side rendering (:
Anyway I never tried angular, and this tutorial made me try it. Is explains very very well how to get started, that's true.
Or rather - even if Google figures out how to index these pages, why should every other consumer of web content have to also figure it out when it's the fault of the content itself.
i.e. don't break the web.
Break the web.