3 ms·
I still think blogs shouldn't require javascript. I certainly can't read the article in w3m. And to read it in Firefox I'd have to enable javascript for the dom
by e12e 13y ago
I still think blogs shouldn't require javascript. I certainly can't read the article in w3m. And to read it in Firefox I'd have to enable javascript for the domain -- which I occasionally do -- but why should I have to do that to read a bit of text?
I can't read an offline version (reasonably) via wget/curl. I find it doubly ironic considering that the blog actually has a nice clean design -- seemingly focused on content. So why not publish it as content?
As a side note, the text of the article (copy pasted) takes up 7.2k. The main javascript file 591K.
Sorry if this comes off as a bit random anti-javsscript rant, but just because we now have a few apps that benefit from client side logic, doesn't mean that most content on the web does. Surely we can use meteor or whatever to implement (one of) the interfaces to our cms/blog -- and still publish regular content as html+css (maybe with an RSS feed that allows for easy syndication)?