[deleted]
Microsoft Edge's JavaScript engine to go open-source
111–120 of 283 posts
Re: Microsoft Edge's JavaScript engine to go open-source
#112Earlier quoted context omitted.
Well, historically, when Microsoft was still in competition-mode, Internet Explorer was kicking Netscape's ass with the later versions. With the first few versions they were playing catch-up, but if I recall correctly, IE 4 and IE 5 actually had more features and better standards compliance than the current Netscape versions, as did IE 6 at its launch. "IE hell" started once Microsoft won the race.
This is very true. Microsoft are at their best when they're the underdog
All companies take more risk when losing.
Re: Microsoft Edge's JavaScript engine to go open-source
#113Earlier quoted context omitted.
Well, historically, when Microsoft was still in competition-mode, Internet Explorer was kicking Netscape's ass with the later versions. With the first few versions they were playing catch-up, but if I recall correctly, IE 4 and IE 5 actually had more features and better standards compliance than the current Netscape versions, as did IE 6 at its launch. "IE hell" started once Microsoft won the race.
This is very true. Microsoft are at their best when they're the underdog
The path is always easier when there's someone there to show you the way, and a clear example of where not to go. Mozilla had a clear path forward with Firefox against IE, and had Navigator as an example of what not to do. Microsoft is now in that position with Edge.
Re: Microsoft Edge's JavaScript engine to go open-source
#114Earlier quoted context omitted.
I think this is perfectly valid point.We can think of it like this, they are pretty competitive and have shitload of resource. but they are not innovative , the moment , they become leader they lose their interest toward growing and growing, although they have huge amount of resource which help them the moment they become underdog. I think this is cultural problem with Microsoft.
Well, from what I've read on the internet, their culture is changing, at least at the grass roots level. A ton of people promoting Open Source & other similar stuff. It's hard to say what this means for the higher levels, but many people think that Nadella's appointment says that Microsoft does want to change. And luckily for US, Microsoft is and will be the underdog for a while at least, in most markets they are in:…
>And luckily for US
I am having hard time understanding why luckily for US ?
Disclaimer : I am not US citizen nor inside us.
Re: Microsoft Edge's JavaScript engine to go open-source
#115Wait, Edge does better on ES6 coverage than both Chrome and Firefox? Microsoft have seriously stepped up their game, especially seeing as it's now neck and neck for performance with Chrome: http://venturebeat.com/2015/09/10/browser-benchmark-battle-s...
The next Firefox Nightly build should get 84% on that page, much closer to Edge than Firefox 44 (74%). I work on SpiderMonkey and I'm super excited about this news. All JS engines have added more-or-less similar performance optimizations but often implemented differently and I'm really interested to see what the Chakra team did. I'd be happy to write a blog post on it next month, if people are interested.
People are definitely interested. Posts about engine architecture are rare and interesting.
Re: Microsoft Edge's JavaScript engine to go open-source
#116Earlier quoted context omitted.
Engineer on the Chakra team here. As the blog post says, we are definitely interested in going cross-platform. Which platforms would you be interested in seeing first?
I would be very insteresting to see a Chakra-based Node.js project for server side apps, so Linux would be my first vote :)
Microsoft is already working on Node, and it's actually already possible to run Node on Chakra. See https://blogs.windows.com/buildingapps/2015/05/12/bringing-n... and https://ms-iot.github.io/content/en-US/win10/samples/Nodejs....
Re: Microsoft Edge's JavaScript engine to go open-source
#117Earlier quoted context omitted.
Well, historically, when Microsoft was still in competition-mode, Internet Explorer was kicking Netscape's ass with the later versions. With the first few versions they were playing catch-up, but if I recall correctly, IE 4 and IE 5 actually had more features and better standards compliance than the current Netscape versions, as did IE 6 at its launch. "IE hell" started once Microsoft won the race.
Perhaps. But it's also worth noting that United States vs. Microsoft was coincident with the stagnation in Internet Explorer, with the case starting in 2000, during IE 5's tenure. For better or for worse, I think the case had a lot to do with Internet Explorer's long pause. I often wonder how Microsoft's browser, its Internet services, and the company as a whole would be today had that case not been undertaken.
If I understand correctly, MS was found guilty of abusing its monopoly by bundling IE with OS, which has put other browsers to disadvantage.
The way I see it, the only trouble with the case was that it was too late. By that time IE has already won.
Are you suggesting some other consequence of this case, leading to stagnation of IE development? I can't see any...
Re: Microsoft Edge's JavaScript engine to go open-source
#118Earlier quoted context omitted.
This is very true. Microsoft are at their best when they're the underdog
I think this is perfectly valid point.We can think of it like this, they are pretty competitive and have shitload of resource. but they are not innovative , the moment , they become leader they lose their interest toward growing and growing, although they have huge amount of resource which help them the moment they become underdog. I think this is cultural problem with Microsoft.
but they are not innovative
They've had a seperate research department for over 20 years or so, and if memory serves me well quite some innovative things came (and still come) out of there. So I think they is too general in your phrase - there is innovation (also look at recent Surface line etc) but you're right in saying that it doesn't always come out and doesn't make it to the market, probably because the they you mean is some parts of management which sees money flowing in and is like 'hey, cashcows enough, no need to think about the future'. Or something like that. And lately this turned around again.
Re: Microsoft Edge's JavaScript engine to go open-source
#119Earlier quoted context omitted.
No wonder: Microsoft needs "class" syntax in JS, they are a driving for behind TypeScript and ES6. Especially interesting, as Javascript has prototype inheritance. The reason: All of MS code is class-based, and they want it to look similar to C#.
Developers of large JavaScript codebases have come to realize that class-based OO is exactly what they need. Prototype OO sounds interesting in theory, but in practice it tends to not be what's needed. Projects that use it end up trying to poorly imitate class OO. This wouldn't necessarily be a problem, except it isn't done consistently. There are multiple approaches, some of them which don't mesh well with others. C…
Not just that - there are performance implications as well due to browsers being able to use a fixed allocation of memory with classes' properties instead of a dynamically resized amount for objects, which results in less efficient algorithms able to be applied internally for the browser for doing similar operations.
Re: Microsoft Edge's JavaScript engine to go open-source
#120Earlier quoted context omitted.
Engineer on Chakra here- are these the docs you're looking for? https://msdn.microsoft.com/en-us/library/dn249552(v=vs.94).a...
I know it's off-topic, but since you're a Microsoft employee: haven't the MSDN guys ever heard about friendly URLs? Compare: https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Sp... (I'm guessing this would be at least the milionth time they hear about it :) )
MSDN does support friendly names: https://msdn.microsoft.com/library/system.string (works for any .net class)
I think the person who wrote this particular page simply didn't specify a friendly name, which is why it's falling back to the canonical name.