Friday, January 26, 2007

Development time

How the fuck does a developer with years of experience and sought after by many of the big-name web companies, suddenly realize that dealing with IE shit still takes up a shockingly large part of development? Why the fuck does anyone still support this sorry excuse of a browser?

Oh, yeah...people still don't know any better. These people ( or "managers" and "goddamned mislead, fucking ignorant masses", by which I prefer to reference them) use it day after day, not knowing that they see the "Internets" (I want to fucking kill anyone using this word...) through fucked-up glasses, not actually making out a single thing as intended. They get a warped view of things and don't even know that things can look so much better!

IE7 introduces CSS support matched (and largely surpassed) by every other browser for years...big fucking deal. It also crippled its DOM support even more, if you can imagine that, and slowed its scripting/DHTML runtime from "fucking slow" to "holy shit, I think the motherfucking ice caps melted before my animated transition ended" in the process.

Development of something so simple as CSS menus should take, at most, a day. I mean really, nicely done, slick menus. With CSS, something with which IE6 has a nodding acquaintence and IE7 took up the ass because it had to or it would get fucking killed. But in order to support the piece of shit that will exist in full support from Microsoft for altogether too goddamn long, I have to spend hour after hour trying to teach IE6 what the fuck it should do, instead of finishing my work and moving on to something else.

Edited 1/26 to clean up the post from the initial no-sleep version. Now includes slightly more coherent phrasing and punctuation.

Labels: ,


Anonymous Anonymous said...

Thank you. I personally would like to shove an iron rod up IE6's ass, which now has so many asswipe patches it noone with a job has time to figure out how to unfuck it's fucked-up discombobulated shit install or repair the goddamned thing if it's fucked to hell, which doesn't take much for that to happen.
It jams half -assed ie7 patches up it's own ass on updates, then won't take a goddamned reinstall because it detects a newer version of IE6 - and it's so goddamned dumb it cannot figure out that it has all it's goddamned patches stored in a million fucking hidden ass folders with the godddamned dollar sign all over the muther fucking root of the windows install drive.
Man it's needs an iron pipe up its ass so bad.
Oh, if this doesn't post, it's because IE6/ half assed 7 patched to hell started a continuous fuck loop auto browser refresh, and is clicking 5 times a goddamned second while it drains blogger . com of all it's bandwidth.
Good thing grandpas double barrel side by side 12 guage isn't handy right now.

10:42 AM  
Blogger The Hater said...

You know, you could just install something else.

5:26 PM  
Anonymous Anonymous said...

the hater-
It has nothing to do with what we use. The problem is we have to develop for what everyone else uses. If a client is using IE6 and his site looks like shit, he isn't going to care that it's MS's fault.

Really, IE6 should die, and I can't say I'd mind seeing some its idiot users go with it.

2:04 AM  
Anonymous Anonymous said...

If I come to know of anyone who was in the IE6 team, I am gonna fuckin chop his motherfuckin head off! Fuck you cocksucking fagbags!!!!

2:02 PM  

Post a Comment

<< Home