Update: now available for RemoteApp. Today, we’re excited to announce the preview availability of RemoteIE via Azure RemoteApp. This is a free service from Microsoft that allows you to run the latest version of Internet Explorer on the Windows 10 Technical Preview from your Windows, Mac OS X, iOS or Android devices, without the need to run a new OS or heavyweight virtual machine on your device.
Which internet explorer can i download on my new mac mini that can use lion? This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
Going forward, this will be the recommended way for developers who are not running Windows 10 to test the latest IE preview versions. To get started, simply sign up at with your Microsoft account and follow the directions to download the Azure RemoteApp client for your platform. And Windows 7! Why build RemoteIE? In June of this year, we the IE developer channel as a way for developers to get the latest preview builds of IE. On October 1st, we began releasing the builds as part of the where it will through the Windows Insider Program. In addition, we provide virtual machines running stable versions of IE.
We know that developers on Windows 7 want a way to test on the latest builds of IE and that the broader development community is eager to have the latest Internet Explorer available on other platforms. To address these needs comprehensively and efficiently, we built RemoteIE on top of the as the latest evolution of the IE dev channel – bringing a single, low friction solution to Windows downlevel clients as well as cross-platform. Our goal is to make the latest IE widely available for testing to all Web developers, to help make the Web just work for everyone. How RemoteIE works The Azure RemoteApp preview builds on the Windows Server Remote Desktop Services infrastructure while also leveraging Azure’s global scale and utility-grade reliability. The service, released to preview in May, enables you to run Windows applications on a variety of devices from the Azure cloud.
RemoteIE provides access to the latest Internet Explorer on the Technical Preview via Azure RemoteApp. With RemoteIE, you can test the latest preview version of IE from your Windows, Mac, Android or iOS device.
Once you’re set up with the RemoteApp client for your platform, you will be streaming IE from the Azure cloud within seconds. Going forward, we will update the RemoteIE version in line with the latest Windows 10 Technical Preview as new builds are released publicly. A few technical considerations:. IE will be the only application available, though that includes the F12 Developer tools!. RemoteApp requires Windows Server 2012 R2 or newer so no older versions will be available (although you can use the F12 Developer tools to change the compatibility modes).
Sessions are limited to conserve server resources. Sessions idle for 10 minutes will be logged out and no session can last more than 60 minutes – you’ll need to start a new session. Performance will not be the same as running IE natively (e.g.
No GPU acceleration). If you want to run it natively join the to get the Windows 10 Technical Preview or from modern.IE. RemoteIE will not be able to navigate to local sites or domains behind a firewall by default.
Be sure to have a publicly accessible IP address or URL to test with, or consider using a 3rd party tunneling service such as. Because RemoteIE and Azure RemoteApp are in preview, there may be service interruptions. Please check the for answers to other common questions. Let us know what you think We’re excited to bring you the RemoteIE preview: a way to test Internet Explorer preview builds on other platforms via Azure RemoteApp.
Please take it for a spin and let us know what you think via or over in the UserVoice forums for. — Anton Molleda , Program Manager, Internet Explorer. Tip for @Doug and others. Developers can proxy localhost to a secret public endpoint using localtunnel. This service solves a problem for some people.
People who have different problems will continue to complain, irrelevantly. That's the nature of internet comments.
That said, If this project proves to be 'successful' (I don't know what the metric for success is) I would like to see this extended to older IE browsers. Maybe MS doesn't really want us focusing on support for previous browsers? The whole VM for a browser solution is ridiculous, IMO, so thanks for not doing that again.
Well, this is kinda cool. It's cool for that fact that you can test without having to install a VM, but really somewhat useless as the modern IE versions aren't usually the ones that developers struggle with. IE6-8 are the major sore spots or at least 7 and 8 as 6 is pretty well killed off in most places. But hey, if you go through the trouble to get 7 and 8 you might as well throw in 6 too. Include those and I think this announcement would be truly stellar. If you really want to turn heads give us 6-11. Netrenderer has been delivering a service for a long time, for the increasingly less developers wanting to support IE.
It's a plain waste of resources do think whatever means possible to provide users and developers with a browser that nobody wants to use. How about you just ONCE built something that is conforming to standards, so people do not have to switch browsers or hack code just because the somanieth crappy version of IE breaks with CSS, HTML, JavaScript of whatever thing Microsoft thought of breaking that time. I have never cried and laught so hard about the 'compatibility mode' that broke CSS compatibilty in two different ways per mode on code that was W3C complient and rendered fine in Chrome, Firefox, Safari, Opera, Konquerer, or any browser that no one may have heard of that is just W3C complient. Stop wasting users, developers and your own time with IE development, either make it complient or stop developing it all the way. Developers don't want to be writing extra code just because of your arrogance and users don't want to have a bad web experience because of it.
On earlier versions of Windows, the. But, what about Windows 10? There, it's a different story.
On Windows 10, it's not crystal clear what the best web browser is. It is, however, obvious what the worst one is: Internet Explorer 11. Sjvn With Windows 10, you have another choice: Microsoft's replacement for Internet Explorer (IE),.
For now Edge is only available on Windows 10. Since, Edge web browser JavaScript engine, it' possible we may yet see Edge running on Windows 7, 8, and 8.1. Indeed, Microsoft is porting ChakraCore to Ubuntu Linux! When last I looked at in June 2015. Now, Windows 10 has been released and then massively upgraded.
For my tests on this run, I used Windows 10, version 10586.63, the latest update as of mid-January 2016. I ran these performance tests on an Asus CM6730. This desktop PC is powered by a third-generation 3.4Ghz Intel Core i7-3770 processor. This is supported by a Nvidia GeForce GT 620 graphics card. The PC also has 8 GBs of RAM and a one TeraByte hard drive.
Here's how well each browser did on the respective benchmarks.: This JavaScript benchmark builds on the foundation of the no longer supported, It combines several JavaScript benchmarks to report a single score that balances them using geometric mean. Jetstream includes benchmarks from the SunSpider 1.0.2 and Octane 2 JavaScript benchmark suites. This test suite also includes benchmarks from the compiler open-source project, compiled to JavaScript using. It also includes a benchmark based on the open-source project's and a port of the realtime Java benchmark, hand-translated to JavaScript. Larger scores are better on this benchmark.
While Chrome dominated on older versions of Windows, Edge took first place on JetStream with a score of 231.78. A good distance behind came Chrome with 196.86; Opera with 186.29; Firefox with 182.46, and, way in the back, IE with 133.07.: This benchmark, which is based on the now obsolete SunSpider, measures JavaScript performance. To this basic JavaScript testing, it added typical use case scenarios. Mozilla, Firefox's parent organization, created Kraken With this benchmark, the lower the score, the better the result. With Kraken, it was a different story.
Here, Chrome took first with 1,009.8 milliseconds (ms). Chrome was followed by Opera, 1037.0 ms. Edge took third place with 1,052.5 ms. Firefox, even though its parent company wrote the benchmark, came in fourth. It was a distant last with 1826.7 ms. Your best browser bets.: Google's contribution to JavaScript testing also includes scenario testing for today's highly interactive web applications.
Octane is not Chrome specific. For example, it tests how fast Microsoft's TypeScript compiles itself.
In this benchmark, the higher the score, the better. Google may have wrote this benchmark, but Edge took first place going away with a score of 36,544. Chrome rallies to second place with 33,926. The third spot went to Firefox, 31,339. Opera took fourth place with 27,736. IE's results were ugly. With 17,571, it couldn't even reach half the score of its younger brother, Edge.: This benchmark doesn't just focus on JavaScript.
Instead it and everything that matters to web developers, like performance of layout and localStorage.' Once more, on this benchmark, the higher the score the better. Time to upgrade - or else. On this performance test, Chrome kicked rump and took names with a total of 175.73. Opera made a contest of it with a score of 165.13. For once, IE didn't make a fool of itself.
It took the bronze with 117.78. Firefox took fourth place with 115.13. Oddly enough Edge turned in its worse score on this benchmark: 102.23.: Finally, I checked to see how well each browser complies with today's. This 'test' isn't a benchmark as such.
It just shows how close each browser comes to being in sync with the HTML 5 standard. A perfect score, which no one got, would have been 550. Chrome took home the gold by a nose over Opera, 521 to 520. Firefox came in third with a score of 468 and Edge was fourth with 453. Coming in dead last, once more, was IE, 343. First things first: The browser you don't want to run on Windows 10 is IE 11. It simply isn't competitive with its rivals.
By the tale of the benchmark, it's between Chrome and Edge. Benchmarks aren't everything. For example, as ZDNet's Mary Branscombe, observed recently, 'I was surprised by just how many other, from tab groups that collect together pages I opened from one search, to being able to pick from a list of the tabs I closed recently rather just the last slip of my finger, to being able to search through my history.' What I miss -and why I can't consider Edge for my primary Windows 10 web browser - is its lack of support for extensions.
On Chrome, my main browser on all platforms, I use over a dozen extensions every day. They allow me to, invoke the,. I'm not moving to a web browser without extensions in this lifetime. There are also some sites, most noteworthy is Facebook, which. Still, that isn't so much Microsoft's problem as it is Facebook playing fast and loose with web standards. Of course, that's not going to matter to you if you're having fits making Facebook comments.
Taken all-in-all, Chrome's my first pick for Windows 10. However, I can see why some of you would prefer Edge. I will be watching Edge closely. I'm told by friends at Microsoft that the company is putting lots of resources behind it. By this time next year, Edge may be the unqualified best Windows 10 web browser, but it's not there yet. Related Stories:. Related Topics.
By registering you become a member of the CBS Interactive family of sites and you have read and agree to the,. You agree to receive updates, alerts and promotions from CBS and that CBS may share information about you with our marketing partners so that they may contact you by email or otherwise about their products or services.
You will also receive a complimentary subscription to the ZDNet's Tech Update Today and ZDNet Announcement newsletters. You may unsubscribe from these newsletters at any time. ACCEPT & CLOSE.