Earlier quoted context omitted.
It's hard to say, but Apple has definitely learned that people don't like paying for minor-ish OS upgrades. I hope Microsoft has learned from that.
I would definitely pay Apple for an upgrade of snow leopard.
Delivering Fast JavaScript Performance in Microsoft Edge
21–30 of 48 posts
Re: Delivering Fast JavaScript Performance in Microsoft Edge
#22And you need to install windows 10 to get the new browser. Is Microsoft coupling their browser again?
It seems like they are. To those people down voting this comment because it comes off as a snark, it has some merit. Web developers need a new machine just to test the new IE. We already have to use multiple VMs or some other solution to test IE6-11 since you can't have more than one IE installed at a time. This just makes web development that much more difficult since now if a bug is reported in the new IE the engin…
1. I'm not sure what you mean by saying Microsoft should be "universal, across all OSs" about them releasing their new browser with their new OS. It's completely reasonable for MS to make the break with their bad browser design to occur at an OS boundary, since what was made their design exceptionally bad was largely coupling of components in to the OS.
2. You're just being completely unfair talking about the versions. The answer is just that Microsoft uses different version schemes than Google and Mozilla with regards to browsers. Your comparison about the gaps in IE compatibility would be like saying Chrome 30 isn't the same as Chrome 20. In your comment, you're comparing different sized steps, based on the assumption that an integer is a reasonable unit to compare the numbers based on. Shame that version numbers aren't numbers in that sense that that tactic doesn't work.
3. Continual updates pushed to the browser already happens under Microsoft's suggested running of Windows -- both minor upgrades (which are the equivalent of the Chrome and FF upgrades you reference), and the suggestion for major upgrades. It just doesn't happen across the board right away because of IT policies in place. This is a concession to major corporate clients who don't want tens of thousands of copies of their software across the globe randomly changing at the behest of some other company, and prefer to manage their own upgrades.
Re: Delivering Fast JavaScript Performance in Microsoft Edge
#23Earlier quoted context omitted.
I would definitely pay Apple for an upgrade of snow leopard.
Unfortunately, Apple doesn't give you the option of voting with your money anymore.
Serious I think I am not alone in wanting to be able to run snow leopard on recent hardware. Apple please make software as good as your hardware.
Re: Delivering Fast JavaScript Performance in Microsoft Edge
#24Earlier quoted context omitted.
You've always needed a reasonably recent version of OS X to use up-to-date versions of Safari. The window for "reasonably recent", right now, is Windows 10. There is no basis in fact to claim that Edge+1 will not support Windows 10, too.
No need to be defensive. I'm simply stating the following sentence is true: Windows 10 and Edge are coupled.
The reason that Edge requires Windows 10 and not Windows 8 is that Microsoft bungled Windows 8 structurally, and they don't want to write their software for "sinking ship compliance".
Re: Delivering Fast JavaScript Performance in Microsoft Edge
#25Earlier quoted context omitted.
We still don't know how that is going to work yet. Will they cut off updates at some point. Do users have to pay for Windows 10.1? Will all future versions of Windows forever be free for those who bought Windows 7/8? etc
Free for one year.
Re: Delivering Fast JavaScript Performance in Microsoft Edge
#26But the thing is, other browsers don't stand still and IE releases are so infrequent, that even if IE really is super-fast at release, within six months it's an also-ran. Maybe Edge will break this pattern? It'd be nice.
IE11, from November 2013: http://ie.microsoft.com/testdrive/Benchmarks/sunspider/Defau...
IE10, from 2012: http://www.extremetech.com/internet/140337-ie10-on-windows-7...
IE9, from 2010: http://blogs.msdn.com/b/ie/archive/2010/03/18/the-new-javasc...
Re: Delivering Fast JavaScript Performance in Microsoft Edge
#27Earlier quoted context omitted.
Free for one year.
Incorrect. Free upgrades for one year, with free updates after that for device lifetime. [1] 1. http://windows.microsoft.com/en-us/windows-10/about (Under Free upgrade offer)
Re: Delivering Fast JavaScript Performance in Microsoft Edge
#28And you need to install windows 10 to get the new browser. Is Microsoft coupling their browser again?
It seems like they are. To those people down voting this comment because it comes off as a snark, it has some merit. Web developers need a new machine just to test the new IE. We already have to use multiple VMs or some other solution to test IE6-11 since you can't have more than one IE installed at a time. This just makes web development that much more difficult since now if a bug is reported in the new IE the engin…
False.
Re: Delivering Fast JavaScript Performance in Microsoft Edge
#29Re: Delivering Fast JavaScript Performance in Microsoft Edge
#30Earlier quoted context omitted.
No need to be defensive. I'm simply stating the following sentence is true: Windows 10 and Edge are coupled.
You're trying really hard to make it sound like a bad thing that Microsoft finally stopped their awful practice of dragging forward a huge stack of backward compatibility, wrote a new API to replace the cruft, and is working on writing new technologies to use this. The reason that Edge requires Windows 10 and not Windows 8 is that Microsoft bungled Windows 8 structurally, and they don't want to write their software f…