3 ms·

While I agree with him on some points most of his arguments are just absurd. Javascript is now a bad thing too, because websites don't license it under the GPL?

• dredmorbius 13y ago
  It's not JS but the Javascript applications (which are almost always non-free) that he objects to. Particularly where websites disable functionality unless you're accessing them with JS enabled. As an example of the latter, I was setting up some custom search engines for Chrome (you can enter the search URL of any site and replace the keyword with "%s"), which is handy for quickly dialing in on content on a specific site, etc. And I've got a large (1000+ articles) Readability list. Which I would like to be able to at least run title searches on (that's all that Readability supports). The problem: Readability's search access is implemented fully in Javascript. I can't search by URL, which means rather than search from the address bar (as I can for many sites) I've got to navigate to my reading list (oh, they set up the landing page so you hit a "recommended reading list" first, so now it's two steps to get to where I want to be), then run your search. It's a small bit of friction, but it's an annoyance, and gratuitous. And if the site wasn't relying on JS, my ability to interact with content I've curated myself would be much greater (search from commandline tools, etc.).