FireFox is now my browser of choice for Windows
I have finally had enough with Internet Explorer. All the Windows computers at home will now run FireFox as the default browser. In the last couple of months, IE has been left open with security holes that have infected several of my computers. Honestly, if it were not for .nET programming and playing online games I would throw out all my Windows computers and only use Mac OS X. I love programming in .NET and I can't see that changing and time soon. Sorry Open Source dudes, your not there yet! Not to say it will not be in a couple of years!
Also IE is REALLY starting to show its age. I used to bash the Netscape users at work in 1999 on how slow the browser was and how they were not up to standards when it came to DHTML and CSS. Well now IE is the slow one and don't get me started how poorly IE has kept up with Web standards. Half the sites I go to these days, they look terrible in IE because of its lack of support for CSS 2.0.
I will still use Safari on my Mac though. I feels faster and more responsive than FireFox. The problem with Firefox for the Mac is that it does not seem as well polished at the version that is available for Windows.
Firefox on the Mac does have features that work better than Safari. For Example: Using the blogger posting page. I am doing this post from Firefox because Safari does not support the rich DHTML editor.
All I can hope for from Microsoft is that they realize IE is outdated and to have to keep up with standards. I don't want them to invent new standards, but just keep up with them! A little competition is a good thing. What I don't want to see is the browser camps going in two different directions like what happenned in 1998 with IE and Netscape. It made developing for sites hell to work on.
The only good thing I found with IE having 98% of the market share was that it made my life easier when developing sites. It was no longer an issue if it also had to work in Netscape. Although this is changing again! We are now seeing more requests that it must work with Safari and Firefox. Our last major web project that was a big deal. We had no idea that their client base was over 80% Mac users until half way into development. During testing, things did not work they way they were supposed to in the Mac. It took a lot of debugging and changing the way we presented the pages to get it to work right on both platforms. I have a feeling we will be back to these days again! That however, is not a good thing in my mind!
Also IE is REALLY starting to show its age. I used to bash the Netscape users at work in 1999 on how slow the browser was and how they were not up to standards when it came to DHTML and CSS. Well now IE is the slow one and don't get me started how poorly IE has kept up with Web standards. Half the sites I go to these days, they look terrible in IE because of its lack of support for CSS 2.0.
I will still use Safari on my Mac though. I feels faster and more responsive than FireFox. The problem with Firefox for the Mac is that it does not seem as well polished at the version that is available for Windows.
Firefox on the Mac does have features that work better than Safari. For Example: Using the blogger posting page. I am doing this post from Firefox because Safari does not support the rich DHTML editor.
All I can hope for from Microsoft is that they realize IE is outdated and to have to keep up with standards. I don't want them to invent new standards, but just keep up with them! A little competition is a good thing. What I don't want to see is the browser camps going in two different directions like what happenned in 1998 with IE and Netscape. It made developing for sites hell to work on.
The only good thing I found with IE having 98% of the market share was that it made my life easier when developing sites. It was no longer an issue if it also had to work in Netscape. Although this is changing again! We are now seeing more requests that it must work with Safari and Firefox. Our last major web project that was a big deal. We had no idea that their client base was over 80% Mac users until half way into development. During testing, things did not work they way they were supposed to in the Mac. It took a lot of debugging and changing the way we presented the pages to get it to work right on both platforms. I have a feeling we will be back to these days again! That however, is not a good thing in my mind!
3 Comments:
It sucks that ASP.NET validation controls and generated javascript isn't cross platform. It wouldn't have been that hard to do it. Supposedly Whidbey will be a lot better at this.
Tell me about it. There was supposed to be a feature in ASP.NET that if your browser was not IE, it would use generic Javascript. Instead they went the other way and required no Javascipt at all and required a round trip back to the server. Maybe now with the depend for Firefox, MSFT will be forced to standardize and use Javascript that all (newer) browsers can understand.
Supposedly the validation control logic (which is in a separate file) will support other browsers in Whidbey.
Haacked (I posted the 1st comment too).
Post a Comment
<< Home