Live data from Hacker News

How Angular Lets Us Iterate Like Crazy

blog.chartbeat.com

21–30 of 50 posts

Re: How Angular Lets Us Iterate Like Crazy

#21

I'm not so sure iterating like crazy is a good thing.

Well, the alternative is working for days / weeks on a feature that the end-user may not even use (is the message I'm getting from this article). Being able to create and alter a feature quickly is important in an agile environment.

Re: How Angular Lets Us Iterate Like Crazy

#22
post #2

Is this website the result of your crazy iterations? http://i.imgur.com/jqy2kwo.png

I'm not using Ghostery and I'm seeing the same thing. Could be Adblock I'm using from Chrome store. https://chrome.google.com/webstore/detail/adblock-plus/cfhdo...

Re: How Angular Lets Us Iterate Like Crazy

#23
post #19

"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…

When I see "she" it makes me reflexively stop and look back to make sure I haven't missed something, wondering, "who is this 'she', I must have skipped the paragraph introducing the subject."

This is definitely bad for readability, the user, and all that. Please, anyone reading this who complains about line-heights and font-sizes, pay attention to grammar as well.

Re: How Angular Lets Us Iterate Like Crazy

#24
post #19

Earlier quoted context omitted.

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…

When I see "she" it makes me reflexively stop and look back to make sure I haven't missed something, wondering, "who is this 'she', I must have skipped the paragraph introducing the subject." This is definitely bad for readability, the user, and all that. Please, anyone reading this who complains about line-heights and font-sizes, pay attention to grammar as well.

Im one to agree. I can see how a woman would be pleased by seeing this, but, when I scroll up and notice it's a "Nick" who wrote the article, all I can think is; huh? Is this guy trying to be edgy? So I re-read, like you said, and there is no mention of a she.

It's just awkward, please stop with the forced gender equality if that's what that is. If it's just being playful then I guess you can shrug it off.

Re: How Angular Lets Us Iterate Like Crazy

#25
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…

Ionic is pretty good if you're looking for the whole flat iOS7 look

Re: How Angular Lets Us Iterate Like Crazy

#26
post #19

Earlier quoted context omitted.

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…

When I see "she" it makes me reflexively stop and look back to make sure I haven't missed something, wondering, "who is this 'she', I must have skipped the paragraph introducing the subject." This is definitely bad for readability, the user, and all that. Please, anyone reading this who complains about line-heights and font-sizes, pay attention to grammar as well.

When I see a comment like this, it makes me reflexively stop and look back to see if the commenter is trying to make a joke, or is really so dense and petty that they're trying to make this an issue.

Re: How Angular Lets Us Iterate Like Crazy

#27
post #20
post #18

Earlier quoted context omitted.

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 h…

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

Only jQuery haters say that. jQuery is totally compatible with Angular,and Angular ships with its own jQuery lite, replaced by jQuery when available. The only thing you need to do is wrap jQuery calls into a directive. I use jQuery and plugins all the time with Angular, never had a problem ,as long i dont call jQuery from a controller , only in directives.

Re: How Angular Lets Us Iterate Like Crazy

#28

I'm not so sure iterating like crazy is a good thing.

Well, the alternative is working for days / weeks on a feature that the end-user may not even use (is the message I'm getting from this article). Being able to create and alter a feature quickly is important in an agile environment.

There are better ways to discover whether a feature is wanted than hacking up a test version and seeing if the users use it. The idea is to test whether people want it before that stage. You can ask them, but often they'll say yes regardless because things often sound great. On the most basic level, adding a UI element that responds with nothing more than a "Coming soon!" message and measuring if anyone clicks it works brilliantly.

Re: How Angular Lets Us Iterate Like Crazy

#29
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…

> UI Bootstrap, but is still seems work in progress.

If by work in progress you mean that it's not ready to be used, then you're mistaken. I use it in my current project a lot (started 6+ months ago).

Re: How Angular Lets Us Iterate Like Crazy

#30
post #19

Earlier quoted context omitted.

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…

When I see "she" it makes me reflexively stop and look back to make sure I haven't missed something, wondering, "who is this 'she', I must have skipped the paragraph introducing the subject." This is definitely bad for readability, the user, and all that. Please, anyone reading this who complains about line-heights and font-sizes, pay attention to grammar as well.

From the article (the first time "she" is used):

"The developer refuses. She’s worked too hard on Feature X, and dammit, you’ll have to pry it from her cold dead hands!!!"

With the exception of the unnecessary extra !! I don't see what is wrong with the grammer, it's clear in this context that "she" is the developer.

Post reply on HN