I can't speak for the company, but I can give you my perspective. Our team is really excited to finally be OSS and work with the community to make Chakra and JS in general more awesome. Nothing nefarious that I can see. Plus, MIT license!
It's more about abstracting Node from the underlying V8 engine. Then you can use whatever underlying engine you want (maybe one that works better on different architectures, etc).
I'm pretty sure Chakra supports asm.js. It should be possible to use any language supported by llvm without paying a performance hit of calling a native library. Imagine using something like sqlite as pure JavaScript at near native speed.
That's part of why we're really excited by this effort. It will be a big real-world scenario we can use to see how we stack up and hopefully will help guide future improvements.
I assume you've extensively looked at V8 and SpiderMonkey. How would you say Chakra differs? Better documentation? Faster in X? Slower in Y? Overall pros cons? Thank you.
Many differences of course, but whether they matter (or are better or worse) depends on what your requirements are. Performance is better in many aspects. Great language support (most of ES6, bunch of ES7). JSRT APIs are pretty nice as well. If you've got something more specific in mind I could talk to it.
Oh man this is actually a huge area. Arrays are extremely commonly used and also very perf sensitive so we have many representations and optimizations in play. Hard to describe concisely. Maybe a good topic for a blog? That said I would bet given that all the runtimes have similar constraints we all use similar representations and optimizations.
Having used V8, JSC, and Chakra to power our app on various platforms, I'd like to call out Chakra as being both easy to integrate into your app (particularly using WinRT class bindings), and easy to debug (unlike v8 which requires jumping through hoops if you're not chromium).
We all know that MS is pushing hard to get people to upgrade to Windows 10 and Edge, but is there any chance that we will see a softening of this stance and maybe Edge running on Windows 7? In other words, how can we get IE11 out of the world faster?
Hi! Chakra engineer here. That decision arose from a community request when we announced at JSConf that we would open our sources. The request was that we provide an option to build ChakraCore without the JIT pieces which would make it easier to embed in certain types of applications, or to reuse certain parts of the code (parser, interpreter) more easily. Since the JIT is one of the most platform-specific pieces (we need to produce assembly), it made sense to make our near-term cross platform goal not include JIT for now. That will get a large part of the code base on more platforms more quickly.
That's not to say there will never be JIT on Linux. The cross-platform effort is work in progress and we'll see how it goes. :)
94
u/bterlson_ @bterlson Jan 13 '16
If anyone has any questions, I and many members of the Chakra team are around today!