Victory Is Mine!
DOOManiac
Worst. Critic. Ever. Join Date: 2002-04-17 Member: 462Members, NS1 Playtester
<div class="IPBDescription">This will be a day long remembered...</div>After months of on-again off-again effort, I have finally achieved victory at work:
I have finally convinced my boss to officially cut support for Internet Explorer for Mac from our site.
Those of you who aren't web developers may not recognize this as a big deal, and even some of you who are will question why. The main reason is every single time I would write some fancy new whiz-bang technology to improve our site (and ensure my continued employment), I would either have to spend dozens of hours getting it to work in IE/Mac or end up scrapping the project once I got to working prototype stage and found no way around the problem.
To those who don't know a lot about IE/Mac, here's a brief summary:
- Years ago, it was the best mac browser for a time. It got very popular in its heyday.
- It is long past its heyday. It is now far, far behind in its support for modern day web standards.
- Development of it has stopped, so whatever it didn't support, it was never going to support. This meant that our entire site had to be limited to only crap IE/Mac supported.
- CSS Style Sheet support is horrendous (even more so than it is for regular browsers), and things frequently looked awful in it, necessitating a redesign.
The latest thing for me to do is to use raw HTTP requests to set and retrieve data straight from our databases w/o a page reload on the user's browser, in a way very similar to what GMail and Google Maps does. Owners really wanted it, and it works beautifully on every browser except IE/Mac.
Out of our total users, IE/Mac is only 0.2% of all hits anyway (about 30% of all mac traffic though), so to cut features for IE/Mac was really holding our site back. But no longer! Now the chains are free! I can make things, beautifuly, sexy things, that actually work again! Hooray! :D
<span style='font-size:5pt;line-height:100%'>Now to kill off IE/Win ;D</span>
I have finally convinced my boss to officially cut support for Internet Explorer for Mac from our site.
Those of you who aren't web developers may not recognize this as a big deal, and even some of you who are will question why. The main reason is every single time I would write some fancy new whiz-bang technology to improve our site (and ensure my continued employment), I would either have to spend dozens of hours getting it to work in IE/Mac or end up scrapping the project once I got to working prototype stage and found no way around the problem.
To those who don't know a lot about IE/Mac, here's a brief summary:
- Years ago, it was the best mac browser for a time. It got very popular in its heyday.
- It is long past its heyday. It is now far, far behind in its support for modern day web standards.
- Development of it has stopped, so whatever it didn't support, it was never going to support. This meant that our entire site had to be limited to only crap IE/Mac supported.
- CSS Style Sheet support is horrendous (even more so than it is for regular browsers), and things frequently looked awful in it, necessitating a redesign.
The latest thing for me to do is to use raw HTTP requests to set and retrieve data straight from our databases w/o a page reload on the user's browser, in a way very similar to what GMail and Google Maps does. Owners really wanted it, and it works beautifully on every browser except IE/Mac.
Out of our total users, IE/Mac is only 0.2% of all hits anyway (about 30% of all mac traffic though), so to cut features for IE/Mac was really holding our site back. But no longer! Now the chains are free! I can make things, beautifuly, sexy things, that actually work again! Hooray! :D
<span style='font-size:5pt;line-height:100%'>Now to kill off IE/Win ;D</span>
Comments
Well, you can't do that when you're a small company anyway...
Umm... I'm going to have to defend the macs here.
Any media editor (read video, graphic, sound, etc) would use the mac, way before a pc is ever considered. Many of the companies around town, (read small ones) use them for servers as well. Of which my health care company does as well.
Blindly following ideals without finding out if they are true is what leads people to make mistakes.
Hooray for the banning of the IE/Mac combo. :-)
*hands a cookie to doomey*
nem0?
Get your boss to require only firefox support <!--emo&:D--><img src='http://www.unknownworlds.com/forums/html/emoticons/biggrin-fix.gif' border='0' style='vertical-align:middle' alt='biggrin-fix.gif' /><!--endemo-->
nem0?
Get your boss to require only firefox support <!--emo&:D--><img src='http://www.unknownworlds.com/forums/html/emoticons/biggrin-fix.gif' border='0' style='vertical-align:middle' alt='biggrin-fix.gif' /><!--endemo--> <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
that = really bad buisness...
"Sure we can design a site for you, sir. It will be no problem for you that 90% of the visitors won't be able to access it, will it, sir? Sir, why are you getting up from you chair? Sir, where are you going?"
Also isnt it that if you make your website fully W3C compatible you will never encounter compatibility problem in any enviroment?
Hehe well that is what my lectures tell me but I myself as a web developer say screw it cos for one thing if I make a website fully W3C compliant its gonna be one boring website. SO I know wat you are going through,
Ironically, many game developers <b>do</b> try to design for the lowest common denominator, often cutting back on the visuals in the game to provide scaling ability for older system.
I recall reading something about this several years ago, so perhaps things have changed: personally, I think many (maybe even most) game developers think this way even now.
Ironically, many game developers <b>do</b> try to design for the lowest common denominator, often cutting back on the visuals in the game to provide scaling ability for older system.
I recall reading something about this several years ago, so perhaps things have changed: personally, I think many (maybe even most) game developers think this way even now. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
Nowadays they leave the original graphics in the game at a "Maximum Detail" setting, I think.
<!--QuoteBegin--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> </td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->Any media editor (read video, graphic, sound, etc) would use the mac, way before a pc is ever considered. <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
Those days are gone, since the PC has some of the best in audio/video editing equipment and drivers in the industry now.