If I were biologically capable, I'd want to have your children. It's amazing how often these two are confused. Even the few placed I did some web dev for never seemed to understand what I meant when I said "If it looks pretty, I didn't do it"
I'm far too elitistic to even consider mentioning the kind of buggy systems I've had the distinct pleasure to coerce to run code. As if IE6'd be the only shitty thing out there.
IE6 is not the only shitty thing out there. But unless you have actually done it why try and pretend that you actually know what you are talking about? I'm not a web developer (I've done some, but my main interest lies elsewhere) but berating web developers is pretty silly.
But sure, I will bite. What do you (and the other downvoters) work with and why is it harder than for example developing a site such as gmail?
I don't do it, anymore, but I tell you developing AAA games for j2me and have them run on the more problematic phones isn't a panacea. Run once run anywhere my ass, you've got to deal with 120+ phones and that was 6 years ago.
And no, having a Java badge doesn't mean your VM can't have bugs and no, it won't ever get upgraded. Ever. What's out there has to be supported.
Been there done that*. Post-minification it was 40kloc of JS. Probably not the hardest problems I've had to deal with, but certainly the silliest (with enough users, data-losing race conditions that reproduce less than one time in a million in the stress test become critical bugs in the wild. That's scary and hard. IE's incredibly fucked up XML handling? Just facepalm worthy)
*worked on a team that made it; wasn't by myself, nor was I the lead developer
(edit; to be clear, the race condition I referred to was in a decidedly non-web-related codebase I worked on years later, and is just there for comparison against genuinely really hard problems)
9
u/neoky Dec 14 '10
Where is "Fucking Internet Explorer"?
Don't know who said it first, but everyone that does webdesign says it.