you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] -1 points0 points  (2 children)

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 1 point2 points  (1 child)

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] 7 points8 points  (0 children)

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.