Reputation
7,332
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
21 46
Newest
 Good Answer
Impact
~338k people reached

Jun
8
awarded  Caucus
Jun
7
comment How do you keep code with continuations/callbacks readable?
Asynchronous JavaScript design patterns
Jun
6
awarded  Nice Answer
May
18
awarded  Nice Answer
May
17
comment Is it considered bad practice to run different JavaScript for IE
it is NOT ok to check for browser name then run different code. Make it clear there is a difference between browser sniffing and feature sniffing
May
6
comment What's so bad about the DOM?
@tdammers the DOM API is slightly verbose. Your making [massive over exaggerations](exaggerations)
May
6
comment What's so bad about the DOM?
It's more trivial then normalizing the DOM. It doesn't really matter anyway since events are part of the DOM :P. What's not trivial is normalizing ranges -.-
May
6
comment What's so bad about the DOM?
I can't be bothered to rant about people confusing legacy browsers and the DOM. I left a comment. As for legacy browsers, dropping support for them is trivial, just do it. Have the balls to do it. Either you control your development life or IE8 controls it. I control mine.
May
6
comment What's so bad about the DOM?
invoke set's the currentTarget. You just set the currentTarget in the invoke method
May
6
comment What's so bad about the DOM?
implementing event bubbling is like a 100 lines of code :\
May
6
comment What's so bad about the DOM?
Most people that say the DOM is terrible are either ignorant or saying legacy browsers are terrible
May
6
comment What's so bad about the DOM?
events are just as trivial to normalize :\
May
6
comment What's so bad about the DOM?
document.all is in the standards
May
6
comment What's so bad about the DOM?
cross-browser inconsistency have nothing to do with the DOM. That's what we call "legacy browsers". Don't blame the DOM for the existence of legacy browsers. That's like saying "linux sucks because I know legacy distro n and m and they suck".
May
3
comment Is it fair to reduce OOP to mere hierarchical composition of data structures?
It should be noted that there are alternative ways to organize code, namely functions (or even procedures)
Apr
14
comment Incorporating libs into module pattern
The fact that a fragment loading library has a jQuery dependency on it's own means it's shit. Also code like this makes me doubt it.
Apr
14
comment Incorporating libs into module pattern
The main point it's trivial to automate commonJS / AMD compliance with a wrapper / build system. As for jQuery plugins, don't use them, all of them are shit
Apr
14
comment Incorporating libs into module pattern
This is why people maintain commonJS compliant forks of popular open source libraries through the NPM.
Apr
13
comment try-catch in javascript… isn't it a good practice?
it's not bullet proof in other languages either. Port that code to any language that supports asynchronous callbacks and it will fail too.
Apr
13
comment try-catch in javascript… isn't it a good practice?
@zzzzBov There's nothing wrong with throwing errors for case C, crash and burn. I just don't think you should catch errors and recover. For example document.getElementById doesn't throw when the element doesn't exist, it just returns null. The same can done for almost all cases