![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Replace "trees" with "Internet Explorer" and you got it about right.
Those of you who don't get the reference are lame, by the way.
Regardless! I am soon to explode with wrath at Microsoft. See, I program for a living. Currently this invloves less programming and more web design, but I still work with languages and getting programs to cooperate. Currently, I am trying to get a piece of JavaScript/DOM Scripting to work in IE.
See, the funny thing is, I wouldn't need to be tearing my hair out about this shit if IE were a goddamn proper browser in the first place. It has one thing going for it: its extremely forgiving nature in the way of whether you can write HTML correctly (goddammit it's not even that hard) made it possible for millions more people to make webpages.
The thing is, those webpages don't work in any other browsers. You know. The ones who PROCESS THE GODDAMN CODE CORRECTLY.
But IE is the most popular browser, right? So what if the way it processes web languages isn't the way that the W3C recommends and all other browsers adhere to? Majority rules, right?
Well, okay, that train of thought is going in the same direction as this article, which advocates phonetic spelling. The thing is, everyone spells differently. So what if the majority of Americans can't spell the language they speak? We need standards, or else that nice thing we call SHARED LITERACY will go away rather quickly.
Same thing here. It was nice of IE to help the Internet boom along and all, but now it has to deal with the fact that if it parsed code in a sane manner, all those websites it fostered would break =D
For responsible web developers, this means that we usually need to give our "special" browser friend a hand.
In this case, IE is being a complete ass. I had to invent a medium-length Javascript workaround for something that in Safari or Firefox can be accomplished with one line of css:
li:hover {display: block;}
There. Done.
However, I have been trying to get IE to accomplish the same result for the past... four? four or five hours.
( Geekery, for those who care )
Anyway. IE makes my life difficult. Again.
*grumps*
EDIT: OH MY GOD I FINALLY DID IT.
FIVE FUCKING HOURS LATER I have FINALLY MADE IT WORK.
OH MY GOD MICROSOFT I HATE YOU.
I'm going home and drawing some gay porn now. Take THAT, Bill Gates!
Those of you who don't get the reference are lame, by the way.
Regardless! I am soon to explode with wrath at Microsoft. See, I program for a living. Currently this invloves less programming and more web design, but I still work with languages and getting programs to cooperate. Currently, I am trying to get a piece of JavaScript/DOM Scripting to work in IE.
See, the funny thing is, I wouldn't need to be tearing my hair out about this shit if IE were a goddamn proper browser in the first place. It has one thing going for it: its extremely forgiving nature in the way of whether you can write HTML correctly (goddammit it's not even that hard) made it possible for millions more people to make webpages.
The thing is, those webpages don't work in any other browsers. You know. The ones who PROCESS THE GODDAMN CODE CORRECTLY.
But IE is the most popular browser, right? So what if the way it processes web languages isn't the way that the W3C recommends and all other browsers adhere to? Majority rules, right?
Well, okay, that train of thought is going in the same direction as this article, which advocates phonetic spelling. The thing is, everyone spells differently. So what if the majority of Americans can't spell the language they speak? We need standards, or else that nice thing we call SHARED LITERACY will go away rather quickly.
Same thing here. It was nice of IE to help the Internet boom along and all, but now it has to deal with the fact that if it parsed code in a sane manner, all those websites it fostered would break =D
For responsible web developers, this means that we usually need to give our "special" browser friend a hand.
In this case, IE is being a complete ass. I had to invent a medium-length Javascript workaround for something that in Safari or Firefox can be accomplished with one line of css:
li:hover {display: block;}
There. Done.
However, I have been trying to get IE to accomplish the same result for the past... four? four or five hours.
( Geekery, for those who care )
Anyway. IE makes my life difficult. Again.
*grumps*
EDIT: OH MY GOD I FINALLY DID IT.
FIVE FUCKING HOURS LATER I have FINALLY MADE IT WORK.
OH MY GOD MICROSOFT I HATE YOU.
I'm going home and drawing some gay porn now. Take THAT, Bill Gates!
