512 karma · joined September 11, 2014
Windows crippled their desktop experience for Windows 8 and 8.1 and are reversing it in Windows 10. No other operating system crippled their system in this way. So must is an unwarranted intensifier. Mistakes were made, things were learned, what you're saying isn't true.
http://www.reddit.com/r/IAmA/comments/chc3k/iama_fella_getti...
Resolution:
http://www.reddit.com/r/Youngluck/comments/cipv9/sentencing_...
IE updates come in too slow, longer than once a year - it's been a year since IE 11, and IE 12 is not even on the near horizon. Chrome and Firefox have had how many updates since then? Even Safari has updated in that time. Windows 10 is slated for release after April 2015, that's a year and a half since their browser has been updated!
IE selectively implements standards for business reasons and IE has a history of versions sticking around for long periods of time.
IE's developer tools, even in IE 11 are horrible. They're not even a shade of what webkit, blink and mozilla based browsers offer.
Finally, and the most damning of reasons: you need to have a Windows machine or a slow and painful (and expensive) virtualization service to test IE if you don't use Windows to develop. We all use macs, if someone isn't using a mac they're more than likely using some linux distro. I haven't worked with a developer that used Windows as their main development machines in 5 years, and in that case they were actually developing a windows application.
IE doesn't deserve our attention, users can install a different browser or deal with it, but I haven't heard a user complain about it, at all. Once in a long while someone might ask, sheepishly, and not make a big fuss about it when we tell them that we don't really support IE.
I wonder what that's doing to the maintainability of your code base. I'm sure the overall cost is higher than just the pay of a single developer ruining your architecture. Supporting IE6 is more than just about fixing bugs.
And really if taco bell loses search ranking for "taco bell" then the problem is with Google.
https://www.youtube.com/watch?v=cJbGNpmE7f0&t=8m30s
Hundreds isn't really exactly "webscale", but I'm sure they'll iron it out, or it could have just been the application that was at fault. It's one data point however on how meteor scales.