Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How Angular Lets Us Iterate Like Crazy

blog.chartbeat.com

Post reply on HN
Print view View original

11–20 of 50 posts

Re: How Angular Lets Us Iterate Like Crazy

#11

Post by matthewmacleod »

ehsanu1 wrote: post #4
oafitupa wrote: post #2

Is 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 really break many sites, although there are still a couple.

However, in this case, CSS and JS from ChartBeat is being blocked because it's one of the tracking services that Ghostery disallows. You can whitelist, but this is probably the "correct" behaviour if you want to block tracking services.

Re: How Angular Lets Us Iterate Like Crazy

#12

Post by defen »

possibilistic wrote: post #5
ehsanu1 wrote: post #4

Earlier 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.

Ghostery blocks Chartbeat since it's an analytics provider.

Re: How Angular Lets Us Iterate Like Crazy

#14

Post by rhizome »

ehsanu1 wrote: post #10
CatMtKing wrote: post #8

Earlier quoted context omitted.

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.

I think the moral is more that if you're not going to let them track you however they want and using whoever they want, they'd rather not have you as a visitor.

Re: How Angular Lets Us Iterate Like Crazy

#15

Post by pjmlp »

I have been looking into Angular, however I am yet to find it any productive gain as being told here.

From what I was able to find out, there isn't any UI component framework available for Angular with the same set of components offering as jQuery has.

For developer teams that haven't a clue about CSS dark magic as guys with designer background have, this is a big impediment to use Angular.

I have looked into UI Bootstrap, but is still seems work in progress.

Is there any UI component framework for Angular?

Re: How Angular Lets Us Iterate Like Crazy

#17

Post by oafitupa »

ehsanu1 wrote: post #4
oafitupa wrote: post #2

Is 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.

No, that's due to web devs tying the functionality of the website to tracking services. I don't remember the last website that didn't have any tracking services, most of them have many. But that alone doesn't break the Javascript when using Ghostery, let alone the CSS. I haven't analyzed this particular website, but it would typically be that they did everything wrong, like loading the CSS via JS, or that kind of weird things web devs like to do these days, that only works fine if you give up on your privacy and security entirely.

Re: How Angular Lets Us Iterate Like Crazy

#18

Post by sgt »

pjmlp wrote: post #15

I have been looking into Angular, however I am yet to find it any productive gain as being told here. From what I was able to find out, there isn't any UI component framework available for Angular with the same set of components offering as jQuery has. For developer teams that haven't a clue about CSS dark magic as guys with designer background have, this is a big impediment to use Angular. I have looked into UI Boot…

Look at angular-ui.

A lot of people just invoke jQuery from directives. Sometimes I catch myself doing it from the controller, although that is definitely bad practice.

Re: How Angular Lets Us Iterate Like Crazy

#19

Post by marquis »

BlindRubyCoder wrote: post #13

"She" is becoming such a gimmick now.

Given the english language requires a gender-specific pronoun (I grew up saying "They" to the chagrin of my teacher) it always makes me a little bit happy to see She in texts. As a woman it makes you realise how much you don't see it. So it stops being a gimmick once the powers that be let us use a non-gendered pronoun ("they" is perfectly fine to me). Or we see a 50/50 split and rewrite the history books accordingly?

Anyway, on topic: we also feel the same way about Angular. Having our APIs abstracted from the beginning into services/factories means we just throw code into a new directive or controller and boom: instant functionality that doesn't cost us a million hours.

Re: How Angular Lets Us Iterate Like Crazy

#20

Post by pjmlp »

sgt wrote: post #18
pjmlp wrote: post #15

I have been looking into Angular, however I am yet to find it any productive gain as being told here. From what I was able to find out, there isn't any UI component framework available for Angular with the same set of components offering as jQuery has. For developer teams that haven't a clue about CSS dark magic as guys with designer background have, this is a big impediment to use Angular. I have looked into UI Boot…

Look at angular-ui. A lot of people just invoke jQuery from directives. Sometimes I catch myself doing it from the controller, although that is definitely bad practice.

Thanks for the reply. Angula-UI seems a bit too simple in terms of available set of components.

I got the idea that although you can use jQuery, it is an anti-pattern and not guaranteed to always work. At least from what I could find in SO and blogs.

My main problem is that I and many others in our teams, don't have any problem doing native UIs, but always get lost in the HTML/CSS/JavaScript jungle without designer help. Regardless of the experience level in web projects.

Post reply on HN