Announcing RemoteIE: Test the Latest IE on Windows, Mac OS X, iOS and Android

Azure VM instances that run in a VPN have major network issues that are caused by the MS infrastructure.

Depending on the latency you won't get the 'feel' for many websites, important nowadays with CSS transitions and WebGL.

MSIE is circling the train in terms of marketshare. The VMs MS provided for testing were a godsend, but forcing devs to give up their work flow would likely result in them just dropping MSIE support.

agreed. That's why I'm always using CoRD (http://cord.sourceforge.net) for any kind of RDP use on the mac (I don't know whether it would work with this remote IE thing, but for sysadmining here and then, CoRD > Remote Desktop any day)

I don't want yet another email address to use a service, Flickr having required a Yahoo.com email address is a prime example, as is Azure.

1) You have to download a complete system image of a machine running the specific versions of Windows and IE you're interested in testing against. Each of these images can require downloading up to 4 DVDs worth of data just to get it bootstrapped, which can take forever even on a fast pipe.

2) Want to test against a different version of Windows, or IE, or both? Now you get to download 4 more DVDs, all over again! (Yep, if you started testing, say, IE9 on Windows 7, and now you want to test against IE10, you have to download a whole new virtual machine from scratch.)

3) For reasons known only to Microsoft, they don't distribute the VM images as unified packages; instead, they're a bunch of DVD-size RAR files that have to be assembled into a complete VM image after downloading. One of those RARs get corrupted en route? Back to downloading!

4) RAR files? In 2014? For serious? Yes, RAR files, for serious.

5) Now you've made it through the epic download, assembled your VM image, and are ready to get started. Hey, guess what! Microsoft is so paranoid about the chance that you're an Evil Pirate™ rather than a legitimate developer that they put a special surprise in the VM, just for you: when it reaches the end of the calendar quarter, the VM self-destructs. Yes, you read that right -- after all that, this VM that you marched through Hell to put together becomes useless after three months at most. So at that point, you get to do all the stuff listed above again.

(Yes, I know there are hacks you can make in the registry to extend this time for an extra quarter or two. It's still insulting.)

The whole process is such a pain that people have written tools like ievms (https://github.com/xdissent/ievms) just to automate the endless, tedious downloading-unpacking-installing-self-destructing-downloading-etc. cycle. And vendors like BrowserStack (http://www.browserstack.com/) make good money charging people to do the same thing they could conceivably do with the VMs, just because using the VMs hurts so much people will happily pay to avoid it.

And the kicker: all of this nonsense, of course, is only necessary because you can't install two versions of IE side-by-side. And the only reason you can't install two versions of IE side-by-side is because Microsoft, back when it was Pure Evil, decided to make it that way to force people to upgrade Windows when they wanted to upgrade IE.

Microsoft management are considerably more enlightened these days than they were back then. But this huge, ugly, painful, completely unnecessary wart on the Windows development experience that they forced upon the world back then still persists, either because someone in Redmond thinks it's a good idea, or just out of sheer laziness.

But that will never happen. The sad fact is that you have to cater to your audience, and almost all people will just click back and look for another site if your site doesn't render perfectly in their browser of choice (or in the case of IE, the only browser they've ever known, even though they didn't choose it). So much time and effort wasted due to MS's anti-competive practices and incompetence.