arstechnica.com— Microsoft released a preview of their redesigned site. Lots of AJAX, looks good, but doesn't work with Firefox. You can scream bloody murder now.
Jul 25, 2006View in Crawl 4
@TubaTechnoMan you don't waste a second in jumping to MS's defense, ever. Did you even read the comments above? Once you mask you Firefox and Opera, everything works like a charm. Its not a compatibility issue, its just MS using its large customer base and its marketing hype about its own products to somehow make other browsers look dinky.
Let me tell you guys about a little fact of life. Every project has a cycle. Development, testing, acceptance, deployment, production. I see plenty of places to catch these mistakes.What is it with you MS fans anyways. At least we are fans of a good idea, better software etc. You are fans of a corporation. WTF is that?
additional note--There are times and reasons to deny access to a site by a browser. Reasons:*Your site uses ActiveX (and it better be for a DAMN good reason)*You're a smalltime, inexperienced developer without the time or know-how to make it compliant. (and theres nothing wrong with that)*You need to use IE6 only tagsNow, this page doesnt use ActiveX, its perfectly compliant with Firefox, and Microsoft clearly has experience. This is just like when I went to check on the status of my MCP at a microsoft subdomain. It denied access to firefox, but not to IE6, or IE7. And guess what--IE7 rendered the page TERRIBLY, while firefox did fine. There was activeX on the page, but it was unnecessary, and trivial--it was to verify phone numbers.Microsoft is just being mean, anal, and spiteful, and its intentional. They know DAMN well that firefox can handle most pages thrown at it, even if theyre done by Frontpage (which sucks ass). Its been QUITE a long time since ive seen a page that rendered badly in Firefox--in many cases, it seems to do better than both IE6 and Opera9.Again, this isnt an issue of development. Its Microsoft trying to make life uncomfortable for anyone daring to use non-IE, and to try to spread the image to non-savvy users that Firefox and Opera suck. Its actually a little suprising that this dirt flinging is more important to them than getting their message out to everyone...
Now that's another reason to use Firefox - so you can't visit this M$ website - actually since I don't have to anyway and have no intention to, its a bit of a dud feature right?
How can they write AJAX that doesn't work in firefox? I have limited experience with AJAX, but I can still write (simple) scripts that work in FF, IE, safari and opera. Professional programmers should have no trouble at all. They probably did it on purpose... Like to make people use IE or something...
I think AJAX was just a big unintentional mistake by Microsoft. They put in XMLHttpRequestObject in I.E just to make outlook web access have an edge over its competitors and not work on non-ie browsers and then it became a standard and totally changed the web. They probably thought, who's going to write full fledged applications in JAVASCRIPT?? It's like any little inch that Microsoft gives on its iron grip spawns whole new industries.
Nothing much except the satisfaction of knowing that we will always be years ahead you MS users in pretty much everything. At least we speak for better software. Most MS apologists, are I think, working on MS technologies and as such feel a need to defend a greedy, monolithic corporation for no reason at all.
hchaudh1Jul 25, 2006
@TubaTechnoMan you don't waste a second in jumping to MS's defense, ever. Did you even read the comments above? Once you mask you Firefox and Opera, everything works like a charm. Its not a compatibility issue, its just MS using its large customer base and its marketing hype about its own products to somehow make other browsers look dinky.
Closed AccountJul 25, 2006
The original microsoft.com only throws 2 errors<a class="user" href="http://validator.w3.org/check?uri=http%3A%2F%2Fwww.microsoft.com&charset=%28detect+automatically%29&doctype=Inline">http://validator.w3.org/check?uri=http%3A%2F%2Fwww.microsoft.com&charset=%28detect+automatically%29&doctype=Inline</a>
hchaudh1Jul 26, 2006
Let me tell you guys about a little fact of life. Every project has a cycle. Development, testing, acceptance, deployment, production. I see plenty of places to catch these mistakes.What is it with you MS fans anyways. At least we are fans of a good idea, better software etc. You are fans of a corporation. WTF is that?
ronin2040Jul 26, 2006
additional note--There are times and reasons to deny access to a site by a browser. Reasons:*Your site uses ActiveX (and it better be for a DAMN good reason)*You're a smalltime, inexperienced developer without the time or know-how to make it compliant. (and theres nothing wrong with that)*You need to use IE6 only tagsNow, this page doesnt use ActiveX, its perfectly compliant with Firefox, and Microsoft clearly has experience. This is just like when I went to check on the status of my MCP at a microsoft subdomain. It denied access to firefox, but not to IE6, or IE7. And guess what--IE7 rendered the page TERRIBLY, while firefox did fine. There was activeX on the page, but it was unnecessary, and trivial--it was to verify phone numbers.Microsoft is just being mean, anal, and spiteful, and its intentional. They know DAMN well that firefox can handle most pages thrown at it, even if theyre done by Frontpage (which sucks ass). Its been QUITE a long time since ive seen a page that rendered badly in Firefox--in many cases, it seems to do better than both IE6 and Opera9.Again, this isnt an issue of development. Its Microsoft trying to make life uncomfortable for anyone daring to use non-IE, and to try to spread the image to non-savvy users that Firefox and Opera suck. Its actually a little suprising that this dirt flinging is more important to them than getting their message out to everyone...
zhulienJul 26, 2006
Now that's another reason to use Firefox - so you can't visit this M$ website - actually since I don't have to anyway and have no intention to, its a bit of a dud feature right?
srg13Jul 26, 2006
How can they write AJAX that doesn't work in firefox? I have limited experience with AJAX, but I can still write (simple) scripts that work in FF, IE, safari and opera. Professional programmers should have no trouble at all. They probably did it on purpose... Like to make people use IE or something...
narratorJul 26, 2006
I think AJAX was just a big unintentional mistake by Microsoft. They put in XMLHttpRequestObject in I.E just to make outlook web access have an edge over its competitors and not work on non-ie browsers and then it became a standard and totally changed the web. They probably thought, who's going to write full fledged applications in JAVASCRIPT?? It's like any little inch that Microsoft gives on its iron grip spawns whole new industries.
hchaudh1Jul 26, 2006
Nothing much except the satisfaction of knowing that we will always be years ahead you MS users in pretty much everything. At least we speak for better software. Most MS apologists, are I think, working on MS technologies and as such feel a need to defend a greedy, monolithic corporation for no reason at all.