5 ms·
With IE, a testing environment costs my company about $300 per developer. I.e., miniscule relative to the cost of actually having a developer.
by yummyfajitas 15y ago
With IE, a testing environment costs my company about $300 per developer.
I.e., miniscule relative to the cost of actually having a developer.
- jayferd 15y agofair.
- barista 15y agoSo you just agreed the premise of your whole argument above is not valid. Just saying.
- jayferd 15y agothat's a little harsh, don't you think? The topic in question is a little more subtle than that. The comments about the developer tools and the wonky VM setup still stand. Also, they say money is fungible, but it rubs me the wrong way to be paying MS for the privilege of testing my site on their browser.
- irrelative 15y agoHe said that a testing environment costs $300. If developer time were free, then yes, he would have agreed that his argument is invalid. Developer time is rather valuable, especially when considering opportunity costs.
- masklinn 15y agoA developer is not a testing environment, and the developer price is paid for testing in Firefox, Chrome, Safari, Opera or what have you. MSIE is no different on that front.
- irrelative 15y agoOf course a developer isn't a testing environment. Developers don't cost a fixed $300. If there are differences between IE and (Chrome|Firefox|Opera), then it will require additional developer time. Just testing for those differences will require additional developer time. I don't want to demonize IE. Supporting any browser requires testing. IE has been especially reluctant to adopt web developer trends and needs to work hard to regain developers' trust. Supporting it isn't just the cost of a testing environment.
- yummyfajitas 15y agoThe majority of his argument is sound, I'm just engaging in the standard HN practice of nitpicking the details.
- ken 15y agoOr compared to the cost of the developer's time for testing and writing code for it. It's annoying that supporting IE costs one Windows license. It's painful that it's so far from standards compliance.
- mcpherrinm 15y agoMicrosoft provides free Virtual Machine images for testing Internet Explorer. http://www.microsoft.com/en-us/download/details.aspx?id=11575 http://www.microsoft.com/en-us/download/details.aspx?id=1157...
- lukeschlather 15y agoAre you free to use those on non-Microsoft host operating system? I thought the last time I checked the host had to be Windows Professional. Also you have to re-download the image every 3 months, and get it set up again. I can't just toss a virtualbox image on my personal Ubuntu machine and test in IE6-8. I need a Windows computer to test my personal sites (which are barely worth development time.)
- tiernano 15y agoIt is setup like a trial edition of Windows. It can be installed on anything really. Microsoft say the requirements are Windows XP and Above, but i did see code to convert from a VHD to a Virtual Box image. Also, you only need to download every 3 months if you want the latest, patched edition from MS. If you want to do it yourself, you can just recreate the image yourself (sysprep).
- projectedoptics 15y agoThe 3 month expiry is what led to my company paying for licenses. Having to potentially pause development and spend time doing the same setup process 4 times a year is painful (and wasteful since there's no real reason apart from trivial licensing issues - the resulting install is the same).
- deleted 15y ago
- JangoSteve 15y agoOr another way of looking at it, infinity times greater than the cost of Chrome or Firefox testing environments.
- masklinn 15y agoExcept Chrome and Firefox both regularly have issues showing up on one platform and not the other, so "Chrome or Firefox testing environments" include the browser and all 3 primary platforms at the very least. Oh look at that, one of those platforms being Microsoft Windows you've already paid for the license you need for testing FF and Chrome.
- JangoSteve 15y agoI can count on one hand the number of times I've had Windows-specific Chrome or Firefox issues in the past 7 years.
- nirvdrum 15y agoThat may be the case, but it's quite possible you just didn't catch them. Most people really don't do a rigorous comparison and even if they do, it's so menial a task that the brain shuts down and things slip through the cracks. I've dedicated the last 2.5 years of my life to auto-detecting differences between browsers and have tested thousands of sites across a variety of fields. I was kinda surprised at the number of rendering issues I've come across with Firefox and Chrome in various combinations of versions and OS. I've even seen some pretty substantial rendering differences between Win XP and Win 7 in Firefox. Anyway, your experience could be totally different. I've just come across a lot devs that have adopted this hivemind mentality around Firefox & Chrome and as a result, they stop testing thoroughly with them. Without thorough testing you can't know if you have problems, so it's really hard to conclude anything because the key data are missing. There's a gap between perception and reality.
- JangoSteve 15y agoIt's also possible that each issue, once figured out, became something I know how to avoid. There really just aren't that many things that break in a browser across operating systems. Also, in my mind, there is a huge difference between "this font doesn't render pixel-perfect in this os/browser combo", and "the javascript broke". One causes much more customer support cost than the other.