A List Apart and Project7 come to the rescue yet again.
But if you're one of those people whose use of IE forces web devs to support a browser with broken support for basic web standards, shame on you! There are plenty of good alternatives (yes, Konqueror is now available for Windows) out there that support all the big ones - Windows and any Unix-y systems (Mac OS X, Linux, BSD).
Windows-only options include K-Meleon. And if you're not using Windows, there's even more browsers: Safari for OS X, and Galeon and Epiphany for OS X and Linux.
Most of those browsers support CSS2 or CSS2.1; Dillo (as an example of a pretty good web browser) doesn't, but at least it's honest about it, rather than implementing it in a broken way and claiming support. Thus, if you're using Dillo, you're not going to blame the nuts-and-bolts look on the web designer, but instead accept that it's the look you wanted - much like if you wanted to use Links, Elinks, or Lynx. After all, you're making that trade-off for speed and size. Now, granted, in the options above, the only rendering engines listed (other than Amaya's and Dillo's) are Gecko and KHTML (well, and Safari's WebCore, which is very similar to KHTML) - but they are far more standards-compliant than IE's Trident.
A relatively brief document called The Decommoditization of Protocols explains part of why standards are so important. The AnyBrowser Campaign might also be interesting - keep in mind that while it's lobbying for web designers to write code that works in all browsers, writing such code would be much easier if browsers complied with standards.
Here's another reason to get rid of IE: then you get to stop hearing me rant about it.
But if you're one of those people whose use of IE forces web devs to support a browser with broken support for basic web standards, shame on you! There are plenty of good alternatives (yes, Konqueror is now available for Windows) out there that support all the big ones - Windows and any Unix-y systems (Mac OS X, Linux, BSD).
Windows-only options include K-Meleon. And if you're not using Windows, there's even more browsers: Safari for OS X, and Galeon and Epiphany for OS X and Linux.
Most of those browsers support CSS2 or CSS2.1; Dillo (as an example of a pretty good web browser) doesn't, but at least it's honest about it, rather than implementing it in a broken way and claiming support. Thus, if you're using Dillo, you're not going to blame the nuts-and-bolts look on the web designer, but instead accept that it's the look you wanted - much like if you wanted to use Links, Elinks, or Lynx. After all, you're making that trade-off for speed and size. Now, granted, in the options above, the only rendering engines listed (other than Amaya's and Dillo's) are Gecko and KHTML (well, and Safari's WebCore, which is very similar to KHTML) - but they are far more standards-compliant than IE's Trident.
A relatively brief document called The Decommoditization of Protocols explains part of why standards are so important. The AnyBrowser Campaign might also be interesting - keep in mind that while it's lobbying for web designers to write code that works in all browsers, writing such code would be much easier if browsers complied with standards.
Here's another reason to get rid of IE: then you get to stop hearing me rant about it.
posted by ismith at 9:02 AM
1 Comments:
yea but they are all so lazy to click that download link, if they weren't lazy firefox would already have a much larger share...
Post a Comment
<< Home