Has anyone wrote up a Chakra vs V8 comparison?
Enable Node.js to Run with Microsoft's ChakraCore Engine
111–120 of 130 posts
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#112Earlier quoted context omitted.
Because a lot of them do, and nearly 100% of servers do.
More of a reason to stop supporting their bugs, and force users and servers to migrate to a more standard-compliant solution. You are just turning V8 into the new IE6 by adapting to it. (Although, in reality, you probably won’t be able to do this, and will end up having to support the non-standard behaviour of V8.)
I think you're confused. It's not a bug, try/catch executes just fine.
try/catch just isn't supported by V8's Crankshaft so some people avoid putting it in potentially hot code.
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#113But it currently doesn't actually support any other platform or have a design that would easily allow that. You are at the front lines of embrace, extend, extinguish. Get away from the Dark Side and the Empire and join the rebels, before you are forced to do something terrible.
We detached this subthread from https://news.ycombinator.com/item?id=10932756 and marked it off-topic.
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#114Earlier quoted context omitted.
>> An implementation of ChakraCore interpreter and runtime, no JIT, on Linux. You should update the wiki if you work on the project then. The stated roadmap goal seems fairly clear and aligns with a typical Microsoft strategy to ensure Windows remains the premium platform for its "open source" efforts. Not being negative that is just the way it has gone in the past so you are fighting an uphill battle. Disclosure: No…
Even the updated Roadmap suggests that Windows remains the primary platform. This Windows-first backend is a bad idea for Node.js, unless the team (and MS) commits to supporting Linux and Mac on par with Windows. That includes not releasing unless they have performance/feature parity on all major OSes, and committing equal resources to all. While MS is nowhere as powerful as it was in the 90s, this is exactly how MS-…
Almost all software has a primary platform. There are a lot of free software apps where windows is either not a priority, or where the devs refuse to implement patches that improve how it works under windows. Additionally, this is just one engine that node supports, in addition to v8, and I assume that with this, other engines can, or could be added in the future. Node's goal is to be a javascript server platform, and that means having hooks both upward and downward to make developers' jobs easier.
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#115Earlier quoted context omitted.
Even the updated Roadmap suggests that Windows remains the primary platform. This Windows-first backend is a bad idea for Node.js, unless the team (and MS) commits to supporting Linux and Mac on par with Windows. That includes not releasing unless they have performance/feature parity on all major OSes, and committing equal resources to all. While MS is nowhere as powerful as it was in the 90s, this is exactly how MS-…
Almost all software has a primary platform. There are a lot of free software apps where windows is either not a priority, or where the devs refuse to implement patches that improve how it works under windows. Additionally, this is just one engine that node supports, in addition to v8, and I assume that with this, other engines can, or could be added in the future. Node's goal is to be a javascript server platform, an…
> Almost all software has a primary platform.
I have no disagreement with software having a primary platform. However, it would make a lot of sense for open source software to choose an open source platform as primary.
Add: I guess what I'm saying is, if you're making enhancements to an existing Open Source project which already works on non-proprietary platforms, it would be better if those enhancements work equally well on non-proprietary platforms.
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#116Earlier quoted context omitted.
Can you explain what you mean by this comment in this context?
We'll see how long it takes to go cross platform. Only then can someone really say but so far this PR doesn't make me feel very comfortable with the Node ecosystem going forward.
Linux support for ChakraCore is planned within the next few months: https://github.com/Microsoft/ChakraCore/wiki/Roadmap
We can see if that actually happens.
Can you explain what makes you feel uncomfortable about the Node ecosystem? I believe Node.js already works on non-Windows platforms.
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#117Earlier quoted context omitted.
Almost all software has a primary platform. There are a lot of free software apps where windows is either not a priority, or where the devs refuse to implement patches that improve how it works under windows. Additionally, this is just one engine that node supports, in addition to v8, and I assume that with this, other engines can, or could be added in the future. Node's goal is to be a javascript server platform, an…
> Almost all software has a primary platform. I have no disagreement with software having a primary platform. However, it would make a lot of sense for open source software to choose an open source platform as primary. Add: I guess what I'm saying is, if you're making enhancements to an existing Open Source project which already works on non-proprietary platforms, it would be better if those enhancements work equally…
There are tons of FOSS/OSS projects for which OSX is the main platform.
Windows isn't exactly a "proprietary" platform, the OS is closed source and proprietary is but it's the wrong definition to use to describe it as a platform especially today with PAAS/IAAS.
Windows isn't free that's true but as far as PAAS (Azure/Azure-Like) goes it's not really a critical part of the pricing, and even for IAAS it's not that important.
One could also say that RHEL, SLES and the likes are proprietary distributions of Linux, they are open source, but proprietary none the less.
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#118Earlier quoted context omitted.
Dont be silly. There may at some point be an effort to build an 'abstract node api interface' and main maintain bindings to various engines... ...but there's no way v8 will be dropped at any point in the foreseeable future. What would you replace it with? This? no way. We're years away from that even being plausible.
The obvious choice would be mozilla's spider monkey.
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#119Earlier quoted context omitted.
For example the chakra engine has a better coverage of es6 than v8. see edge score there https://kangax.github.io/compat-table/es6/
We're working on updating Kangax, but V8 now has 92% ES6 coverage in Chrome Canary (on track for shipping in Chrome M49)! Disclaimer: I work on V8
How so? I just loaded es6 kangax table in Canary "Version 49.0.2566.0 canary (64-bit)" and it reports 62% for current browser.
EDIT: 92% reported for "Version 50.0.2626.0 canary (64-bit)"
nice job!
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#120Earlier quoted context omitted.
> If I were to predict, I'd see Node switching to ChakraCore as its primary engine in a year. Chakra doesn't even compile on Mac OS or Linux, where the majority[1] of instances run. If I didn't know better, I'd say Microsoft isn't interested in Chakra-Node running on other platforms - only on Windows, but with a V8-beating performance or other 'desirable' Chakra-only extensions (extend). Want high performance NodeJS?…
The roadmap for ChakraCore includes getting it to run cross-platform. Additionally, as ChakraCore is Free Software, you're more than welcome to fork it and/or submit patches as needed.
"Patches welcome" is not a particularly compelling response to "it doesn't run on any of the platforms people currently use".