2,542 karma · joined September 28, 2009
Director of Engineering at Shopify
I'd be interested to hear what type of bugs were common in this scenario; my understanding of the runloop is that after the DOM update (at the end of each loop) the UI should reflect the application state.
All software ships with bugs--including the software this guy will create using XCode. Despite that, this type of drivel is still common among software developers. "One (relatively minor) bug exists that happens to annoy me: that must mean their whole QA process is shit!"
Come off it; this type of rant would be warranted if XCode routinely crashed when you paste a paragraph of text into a label--not because it behaves in a funky way.
http://altdevblogaday.com/2011/12/24/static-code-analysis/
While not all of this is immediately applicable to JSHint and the like, it provides some insight into why static code analysis can be seen as helpful.
As you also mention, it's really helpful for code within a codebase to be consistently written. JSHint can help enforce some of that consistency. This is where JSHint really shines.
If your JS is tied to some sort of "build" process (even a short 1-2 second one), catching errors before running the build is incredibly helpful. If you intend to minify your JS code (as you should) before distribution, finding missing semicolons can be very important, indeed. I find the most helpful JSHint errors to be about mistyped variable names. It's so much easier to see that in my editor, fix it, and THEN run it in the browser.
There are definite workarounds such as setting up paging--but the simple approach of using Ember.js bindings to bind a collection to a template will fall to pieces as that collection grows.
FWIW, I'm not an expert on Ember.js or Backbone; just someone trying his hand at hacking the Ember.js code to work more effectively with collections (since some of the use cases I have would be impossible using the current methods of bindings and collections).
For what it's worth, there are a ton of recommendations to do this same thing out there--and for many people it's just not a viable option. This isn't a success story so much as it's using a workaround. Not being part of either the Ruby or Apple dev teams, I won't say whose side this is on to fix: only that it needs to be fixed.
To each there own as to how setting breakpoints works best for them in their workflow--my only reason for commenting was to let people know there were other ways to set breakpoints than adding "debugger" lines all over their code.
For example, doing comparisons (x == null) or (x != null) is a well known shortcut for checking vs null or undefined. There's nothing inherently "bad" about using that shortcut.
Since some folks write JS that has to go through a "build" process, it's easier to set a breakpoint in the debugger than to go back, modify the code, and "re-build" to get a breakpoint.
Several young, socially connected folks give it a shot.
Horny dudes browse the passenger list looking for a "hot chick" to sit next to.
Girls wise up to what the guys are doing and stop signing up.
Guys do what we always do and lose interest in yet another "social activity" completely devoid of women.
I agree with both authors; but I find this particular article far more obnoxious than the one to which its responding--again, because it comes across quite smug.
I completely agree with your assessment of sales commissions elsewhere--and I think we've all seen enough of a share of unfair, incompetent management to understand the rationale. That said, I also agree that there is some serious baggage that comes with commission-based compensation and it's worth a look to dump it.
Moreover (and I'm reading between the lines a bit here) I think part of that statement is referring to sales people ignoring the "hard" sales and focusing only on the "easy" sales. "Are you ready to buy? No? Ok, I'll call again in 6 months" becomes, "Let's talk about your concerns so that maybe you'll buy in a month instead of 6."
My thought is that, just like in every other aspect of the business, your top players will be your highest paid as part of the normal compensation process--and those top people should be the ones closing the bigger deals. Just because you don't get cut a check for that specific deal doesn't mean there wouldn't be rewards for doing so.
...except, of course, our own.
I think part of it comes from the most vocal (and probably most respected) JS developers tend to be library developers and their guidelines for themselves and each other tend to get misconstrued as general guidelines for JS development.
When you're developing in a known execution environment, I don't see any particular issue with extending natives.
Congrats to Groupon on their successful IPO; I still have very strong doubts that they have any means of building a successful, sustainable business. Time will tell better than my attempts at fortune-telling.
It also depends heavily on the complexity of the logo and the painting implications. To say simply that "CSS will be more performant" is categorically incorrect.
It's also completely and totally useless. The person / people who did this are obviously talented and have a lot of expertise. I'd really rather see people with this level of ability contributing meaningful, useful tools / techniques to the community rather than seeing this type of post over and over again.
I can hear the arguments now, "but it shows off the power of CSS!"
No, it doesn't. It shows off what a clever person can achieve by tinkering with a system; but there's no practical value to most of the techniques demonstrated. CSS has a lot of power; but its best demonstrated by projects like the CSS Zen Garden that show off real-world CSS use.
It makes for one hell of a story; but, I think the better story is to think of a man who spent his last 24 hours alive with those closest to him--his family.
I've felt this way a long time about RMS; his comment about Steve Jobs's death was uncalled for--but it really was well-within character. Just like Phelps and Westboro are expected to show up at soldier's funerals to protest, we've come to expect this type of shit from RMS--and I agree with the OP that it's time to stop just accepting it.
[Edit] I want to state that RMS, like everyone, is fully entitled to his opinion and that opinion carries no more or less weight than my own. Moreover, you're completely entitled to agree with him. What I do have a problem with is what the OP described: he doesn't belong at the head of a major organization, nor does he belong at the apex of the free software movement. Beyond my earlier described "inner circle," in the past several years, he's done more to tarnish the image of the free software community than to help it.