How Angular Lets Us Iterate Like Crazy
blog.chartbeat.com
How Angular Lets Us Iterate Like Crazy
1–10 of 50 posts
Re: How Angular Lets Us Iterate Like Crazy
#2Is this website the result of your crazy iterations?
Re: How Angular Lets Us Iterate Like Crazy
#3I'm not so sure iterating like crazy is a good thing.
Re: How Angular Lets Us Iterate Like Crazy
#4Is this website the result of your crazy iterations? http://i.imgur.com/jqy2kwo.png
No, that's due to Ghostery. Recognized it as soon as I saw your image. Ghostery breaks lots of sites, even those it isn't explicitly blocking.
Re: How Angular Lets Us Iterate Like Crazy
#5Is this website the result of your crazy iterations? http://i.imgur.com/jqy2kwo.png
No, that's due to Ghostery. Recognized it as soon as I saw your image. Ghostery breaks lots of sites, even those it isn't explicitly blocking.
Ghostery doesn't break "lots of sites". This is one of possibly two or three pages I've noticed in the last year that have been broken by Ghostery. That's hardly an epidemic. (But perhaps this is an issue of sampling.)
Given Ghostery's popularity, I would almost venture to blame the website for this unintended behavior, not the plugin--even if they're keeping to standards and good behavior.
Re: How Angular Lets Us Iterate Like Crazy
#6Re: How Angular Lets Us Iterate Like Crazy
#7Re: How Angular Lets Us Iterate Like Crazy
#8Earlier quoted context omitted.
No, that's due to Ghostery. Recognized it as soon as I saw your image. Ghostery breaks lots of sites, even those it isn't explicitly blocking.
Ghostery doesn't break "lots of sites". This is one of possibly two or three pages I've noticed in the last year that have been broken by Ghostery. That's hardly an epidemic. (But perhaps this is an issue of sampling.) Given Ghostery's popularity, I would almost venture to blame the website for this unintended behavior, not the plugin--even if they're keeping to standards and good behavior.
Is this due to JavaScript blocking? I mean, the whole premise of using AngularJS is that the client is executing JS..
Re: How Angular Lets Us Iterate Like Crazy
#9Earlier quoted context omitted.
No, that's due to Ghostery. Recognized it as soon as I saw your image. Ghostery breaks lots of sites, even those it isn't explicitly blocking.
Ghostery doesn't break "lots of sites". This is one of possibly two or three pages I've noticed in the last year that have been broken by Ghostery. That's hardly an epidemic. (But perhaps this is an issue of sampling.) Given Ghostery's popularity, I would almost venture to blame the website for this unintended behavior, not the plugin--even if they're keeping to standards and good behavior.
I've noticed many sites that have failed load a video or something similar due to Ghostery, but it has been happening much less after the last major update. It's usually not as drastic as stripping all CSS of course, just breakage that seems like a bug on the site, until you realize you should try again after pausing Ghostery.
Re: How Angular Lets Us Iterate Like Crazy
#10Earlier quoted context omitted.
Ghostery doesn't break "lots of sites". This is one of possibly two or three pages I've noticed in the last year that have been broken by Ghostery. That's hardly an epidemic. (But perhaps this is an issue of sampling.) Given Ghostery's popularity, I would almost venture to blame the website for this unintended behavior, not the plugin--even if they're keeping to standards and good behavior.
Is this due to JavaScript blocking? I mean, the whole premise of using AngularJS is that the client is executing JS..
It's blocking tracking scripts/pixels/etc. If a site's JS happens to rely on some external tracker having been loaded, it can break the site. I think that's what's usually happening here. Moral of the story: don't rely on external scripts people.