Live data from Hacker News

Delivering Fast JavaScript Performance in Microsoft Edge

blogs.windows.com

41–48 of 48 posts

Re: Delivering Fast JavaScript Performance in Microsoft Edge

#41
post #7

Earlier quoted context omitted.

While every OS ships with a browser, I think the OP was asking "do you have to install windows 10" in order to get the new MSFT Browser. IIRC, those examples you listed, you don't need to install the latest OS X to get the latest version of Safari (though you need to have a recently supported OS).

You can't use Safari 8 on Mavericks. In a sense they backported some features to Safari 7 (as well as security updates, etc), but it's a distinct version and a very different browser.

Fair point.

Many versions of Safari are coupled with OS X updates.

Re: Delivering Fast JavaScript Performance in Microsoft Edge

#42

The performance boost from IE11 is nice, but the comparisons to other browsers should be taken with a major grain of salt. Because the thing is, every IE release has "beat the competition" in benchmarks leading up to its release (links below). But 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…

While I completely agree that regular releases and an evergreen browser are extremely important in today's world (and that is the direction that Microsoft Edge is moving towards), I am not sure what point you were trying to make by saying that comparison against competition should be with a grain of salt.

All three blogs that you point to talk about SunSpider benchmark (from Apple), and since IE9, or the day the first blog was published, the story holds true. Across platforms (32-bit or 64-bit), Microsoft Edge and IE remain as leaders in that benchmark across all competing browsers. The nearest competitor is around 40% slower. Here are the nos. across major browsers on SunSpider

MSEdge: 103 FF Nightly : 176 Chrome Canary: 171

Re: Delivering Fast JavaScript Performance in Microsoft Edge

#43
post #29

Exciting stuff. It feels really weird for someone to write a blog in which they discover that 95% of websites use minified JS though. I guess it's nice to see Microsoft making some progress but you have to wonder what's going on over there if they seem to clueless to the state of the modern web.

My understanding is that the same JavaScript code minified by different minifiers will produce different performance results across any browser. This is because minifiers often introduce code patterns that are very different than the JavaScript code that the devs write. The point being made is not about being non-aware of the web, but more about ensuring the web runs faster across different code patterns that are encountered by the JIT compiler while running the web.

Re: Delivering Fast JavaScript Performance in Microsoft Edge

#44
post #33

Earlier quoted context omitted.

With modern.ie, you get free testing VMs and screenshots of any website rendered in IE across many devices. To test Safari on Windows, Apple provides you with many less options (certainly no free browser testing OSX VMs!). They're going above and beyond to make up for past mistakes, for that I'm grateful.

OSX VMs... Now there's an idea. I'd be more than willing to pay a large premium for an officially supported version of OSX that runs in VMware/Virtualbox/Hyper-V/etc. But I suppose it probably isn't in Apple's best interests to offer one.

It exists now, you just need to run it on an OS X machine running OS X + Fusion to be legal.

I have vagrant vm's for OS X back to 10.7. You might be able to run esx on a mac then use vm's that way but I have no idea. In either case what you want has existed for some time.

Re: Delivering Fast JavaScript Performance in Microsoft Edge

#45
post #44

Earlier quoted context omitted.

OSX VMs... Now there's an idea. I'd be more than willing to pay a large premium for an officially supported version of OSX that runs in VMware/Virtualbox/Hyper-V/etc. But I suppose it probably isn't in Apple's best interests to offer one.

It exists now, you just need to run it on an OS X machine running OS X + Fusion to be legal. I have vagrant vm's for OS X back to 10.7. You might be able to run esx on a mac then use vm's that way but I have no idea. In either case what you want has existed for some time.

I should have been more specific. I was hoping for an OS X VM that runs on host OSes other than OS X.

Re: Delivering Fast JavaScript Performance in Microsoft Edge

#46
post #13

Earlier quoted context omitted.

It's easier to 'sell' people free updates without a lot of perceived upsides for the end-user than to 'sell' them that they also have to pay for the update :)

Unless I'm going crazy, I don't think your comment makes grammatical sense. Both of those options are made to sound bad (without upsides, also have to pay?) In any case, I'm not doubting that it's easier to pitch an update if it's free. All I'm saying is that purchase cost isn't the main or only barrier to Microsoft software updates.

Sorry about the weird phrasing. What I wanted to convey is that sometimes from the user's point of view it is not easy to see/perceive any upside from upgrading (even though technically there might be lots). => hence a free upgrade is way easier to say yes to.

Re: Delivering Fast JavaScript Performance in Microsoft Edge

#47
post #44

Earlier quoted context omitted.

It exists now, you just need to run it on an OS X machine running OS X + Fusion to be legal. I have vagrant vm's for OS X back to 10.7. You might be able to run esx on a mac then use vm's that way but I have no idea. In either case what you want has existed for some time.

I should have been more specific. I was hoping for an OS X VM that runs on host OSes other than OS X.

Technically possible but against the licensing.

Re: Delivering Fast JavaScript Performance in Microsoft Edge

#48
post #28

Earlier quoted context omitted.

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…

> Web developers need a new machine just to test the new IE False. http://dev.modern.ie/tools/vms/

A Virtual Machine is the machine I meant, sorry.
Post reply on HN