Re:What We Talk About When We Talk About Ad Blocking
by tomjen3 on Sunday September 13, 2015 @09:18AM
(#10211289)
Angular is for data in an interactive app. I really don't see how you can make an interactive app without Javascript (you could do as HN do and make it reload a new page all the time).
[ Parent
| on HN ]
Re:What We Talk About When We Talk About Ad Blocking
by userbinator on Sunday September 13, 2015 @10:00AM
(#10211418)
The vast majority of the time when I'm looking for something I'm not looking for a web app; I'm looking for a web page that I can instantly read and find what I need. Imagine going to a library and finding out the books had unskippable autoplaying videos and animations every time you turned a page, and you had to wait before you could see the text.
Contrary to the trend, not every site needs to be a web app. I feel like all the features of HTML5 are leading to something a lot like the Flash-only sites that blossomed during the late 90s and early 00s; just as inaccessible and user-hostile, except even more resource-consuming. The fact that it's built into the browser instead of a plugin and standardised does not make any difference to the end result.
Re:What We Talk About When We Talk About Ad Blocking
by pdkl95 on Sunday September 13, 2015 @09:49AM
(#10211388)
It doesn't matter what it's "for" - I've seen quite a few sites where it's being used to render static content. Well, at least what should be static content (i.e. articles/blog-posts, basic index or portal hompages). example: http://www.intel.com
I don't intend to single out Angular. I'm talking about any framework that renders empty pages. For example, http://www.meteor.com/ renders an empty body tag, and I doubt their homepage requires interactivity.
(I'm not talking about anybody that uses a framework but still renders an actual document)