this requirement:
"it also only need to work in Chrome – no IE testing necessary"
sounds like they had a preference for AngularJS. I guess your eventEmitter solution was too advanced for that company.
Ask HN: What's wrong with my JS?
11–14 of 14 posts
Re: Ask HN: What's wrong with my JS?
#12this requirement: "it also only need to work in Chrome – no IE testing necessary" sounds like they had a preference for AngularJS. I guess your eventEmitter solution was too advanced for that company.
That sounds like a huge leap that because they are only going to test the solutions in chrome that he should have used angular.
Re: Ask HN: What's wrong with my JS?
#13this requirement: "it also only need to work in Chrome – no IE testing necessary" sounds like they had a preference for AngularJS. I guess your eventEmitter solution was too advanced for that company.
That sounds like a huge leap that because they are only going to test the solutions in chrome that he should have used angular.
without putting value to Angular, many companies that say "works in Chrome" mean "developer friendly". And from "developer friendly", it seems a small step to Angular. Maybe because many developers don't want to invest time learning real JS.
Re: Ask HN: What's wrong with my JS?
#14"After a car has been added to the wish list, the select box should default to the first alphabetically available car from the same make". Doesn't happen. Leaves the make and returns to top make after selection.
omg, you're right.
Kind of sneaky to put important details in parentheses like they did. I would have let that omission slide, especially considering the typical candidate we get.