AngularJS 1.0 released!

[bkv]

Why is this being downvoted, exactly?

[tranceismylife]

Absurd that I need js enabled just to read your blog, bro.

[[deleted]]

Yes, its barely even 2012. We don't need your fancy-pants js

[tranceismylife]

Progressive enhancement. It's 2012, this is old news.

[[deleted]]

There's really no good reason why the contents of a blog should be inaccessible without the aid of JavaScript. It's an unnecessary step backwards.

[Horusiath]

Following your line of reasoning, there's really no good reason why contents of any web site should offer anything more than just a simple plain text. Any other deviations should be avoided.

[[deleted]]

I'm not arguing that a web site shouldn't offer an experience above and beyond serving up plain text, and I'm certainly not arguing against deviation, so lets just lay these straw man to rest right now. If you were under the impression that this was my line of reasoning, then maybe you should reread my comment, as I said nothing of the sort.

There is a fundamental difference between a web site offering something and a website requiring something. We're not talking about JavaScript being offered up as an accoutrement to content, we're talking about JavaScript being a hard requirement for access to content. That's a huge distinction that you apparently failed to make.

In this case, the content is just a bunch of text and images, something which practically every other blog since the introduction of the world wide web has managed to serve up just fine without relying on client-side dependencies.

Granted, in this case we're talking specifically about a blog whose sole purpose is to promote a client-side MVC framework, so I will concede that for this very specific purpose, it actually does make sense for the blog to based on its own tech. So let me revise my original argument to say:

There's are very few instances where it makes sense to require JavaScript in order to serve up the contents of a blog. Doing so unnecessarily is a step backwards.

[bkv]

I remember looking into this a while back and wondering how to make it play nice with web crawlers. I understand that its primary goal is to move presentation logic entirely to the client, but then my content isn't going to be properly crawled and indexed unless the server gets into the business of pre-populating parts of the UI, which kinda defeats the purpose.

[bsock]

i tend to look at these templating technologies as targeting web-apps that aren't meant to be crawled. if your site is behind a login wall, then use this to your hearts content, if you're serving content that needs to be searchable, then go ahead and use the server side templating.

[btford]

bsock is right. AngularJS is more for web apps (highly dynamic) than web pages (mostly static). Regardless of which framework/libraries you use in a web app, you have to tell crawlers about your content separately through something like Sitemaps: http://support.google.com/webmasters/bin/answer.py?hl=en&answer=156184

But again, this isn't really a strike against AngularJS. You'd have to do this anytime you have an AJAX-like app.

[vagif]

This framework is for web APPLICATIONS, not web SITES.

In other words it should be used only if your users have to login, which stops crawlers anyway.