3 ms·
It's not so much a question of would as could. I'd have to install IE first. And it would take a lot to make me do that.
by pg 19y ago
It's not so much a question of would as could. I'd have to install IE first. And it would take a lot to make me do that.
- eusman 19y agoI suppose this will be the general reaction here. If it's possible we could we have of an insight to YC.news stats of what the majority uses here, I guess Firefox/Safari wins over IE?
- davidw 19y agoYou are of course in an enviable position... I would hope that most people actually working on a web site use something like Wine to be able to test it in IE. No way do I use it one minute more than I have to, though.
- cstejerean 19y agoI almost never test things in IE. I'm counting most of the time on the JS libraries I use to be cross platform and defer to a JS guru when some IE only bug shows up. Most of the time one of the many other people that have to look at a prototype will be running IE and report an issue. It's not worth it for me to bother (is it possible to run IE7 in Linux now? IE6 is obsolete).
- juanpablo 19y agoI run Windows in a virtual machine in Linux to test things. Sure, if you use some library like JQuery or Mootools most of the time your javascript will be cross-platform. But what about the CSS? Of course IE6 is obsolete (since v0.1 of Firefox-Firebird), but that depends of your target market.
- cstejerean 19y agoI was actually referring to Microsoft dropping support for IE6. Even though IE6 market share is still high with no Windows Genuine Advantage requirements for IE7 some sites are dropping support for IE6 and requiring IE6 users to upgrade to IE7.
- xirium 19y agoRunning IE precludes an operating system and hardware on which it runs. If you asked about developing for Firefox only then I'd strongly recommend it. This browser can be run on many operating systems. Most importantly, early adopters who are likely to use this browser are more likely to be an early adopter of your service. For the same reason, I'd recommend developing a Firefox plugin rather than an IE plugin.
- mixmax 19y ago>"If you asked about developing for Firefox only then I'd strongly recommend it." I know that this is a tech site, and that I am probably get modded down for saying this: But that is absolutely ridicolous. Basically what you are doing if you are only developing for firefox is opening a shop where you only let 10% of your customeres through the door. The rest will have to go home, or go to you competition. I mean, seriously... Business 101 guys ;-)
- cstejerean 19y agoNo, the other option is for your customers to install Firefox. Now this isn't always something you can demand/expect of your users. But for example for a free service or during a beta period it's perfectly reasonable. Most IE market share is not early adoption friendly. If they wouldn't fear new technology they would be on Firefox already. Either they never heard of Firefox or don't want to try it out. Neither one is a quality that indicates early adopter.
- greendestiny 19y agoI actually considered doing the web application I'm doing at the moment as firefox only, purely because it heavily relied on SVG. It's very much a niche market where my competitors are desktop applications, and it will be a fairly expensive subscription service so it didn't seem unreasonable to demand users download firefox. Eventually though I just came to realise that the biggest advantage of the web was the ability to have anyone come to my site and be ready to use the product. So in the end I've gone with flash.