I am sure I'm a minority on this thread - but does anyone else think that if the engine is being developed in the open as open source then competition is not a good thing. I believe it's similar to having io.js and node.js - together it is a stronger platform. To this end, I think it would have made a lot of sense for MS to collaborate with webkit/blink and vice versa... that's the true spirit of open source IMO... I don't believe the web is stronger with more rendering engines and more JS runtimes... I think it's weaker. What would make it stronger is more open source and more collaboration. We have to be very happy that MS is taking the first step in this direction. Open Sourcing ChakraCore is a huge first step and now integrating it with other systems as well . I just hope over the next 10 years we see more collaboration between webkit, blink, gecko, and trident... as well as the JS engines...
Enable Node.js to Run with Microsoft's ChakraCore Engine
71–80 of 130 posts
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#72Many posters in that Github Chakra pull request thread appear to be in the "Node is V8 and only V8" camp. This is disappointing. Since when is having a bigger developer community, supporting the latest ES6 standards, and having wider reach for NodeJS a bad thing? Look at what the friendly rivalry has done for the various browsers - the competition benefitted everyone and advanced technology immeasurably.
Because if the argument is better support and wider reach then maybe wait until it runs on more than one platform. Edit: even if they had waited until the JITless builds for OS X and Linux were ready I'd be happier. This definitely feels like jumping the gun.
As long as each JS engine uses the same API (at this point V8's C++ API, hopefully something engine neutral later) what difference does it make?
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#73Earlier quoted context omitted.
Why? Most users aren’t on V8.
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.)
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#74Earlier quoted context omitted.
Because if the argument is better support and wider reach then maybe wait until it runs on more than one platform. Edit: even if they had waited until the JITless builds for OS X and Linux were ready I'd be happier. This definitely feels like jumping the gun.
As long as each JS engine uses the same API (at this point V8's C++ API, hopefully something engine neutral later) what difference does it make?
It shouldn't be merged into core if it doesn't work on the rest of the platforms core works on. Keep it in some experimental branch until it is ready and more important why would they even submit the PR if a ton of tests are failing?
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#75Earlier quoted context omitted.
Embrace, extend, extinguish.
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.
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#76I am sure I'm a minority on this thread - but does anyone else think that if the engine is being developed in the open as open source then competition is not a good thing. I believe it's similar to having io.js and node.js - together it is a stronger platform. To this end, I think it would have made a lot of sense for MS to collaborate with webkit/blink and vice versa... that's the true spirit of open source IMO... I…
>>> I don't believe the web is stronger with more rendering engines and more JS runtimes... I think it's weaker
I disagree. I'm happy to see numerous JS engine implementations that embrace a common standard. If you have just one common code base you also have a common set of bugs. Competition is a great way to raise the bar and try out radically different design approaches. Take GCC and LLVM for example - who can argue that friendly competition hasn't helped them both immeasurably? Link Time Optimization, C++14 compliance - choice is a good thing.
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#77Many posters in that Github Chakra pull request thread appear to be in the "Node is V8 and only V8" camp. This is disappointing. Since when is having a bigger developer community, supporting the latest ES6 standards, and having wider reach for NodeJS a bad thing? Look at what the friendly rivalry has done for the various browsers - the competition benefitted everyone and advanced technology immeasurably.
I'm a node.js developer and I don't really care what interpreter is being used as long as any code submitted to NPM is compatible with any version of node.js regardless of the JavaScript engine.
The only issues would be in ChakraCore were to support additional ES6/7 features that people started to use that wouldn't work on a V8 node.js instance, or the other way around.
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#78Earlier quoted context omitted.
As long as each JS engine uses the same API (at this point V8's C++ API, hopefully something engine neutral later) what difference does it make?
It shouldn't be merged into core if it doesn't work on the rest of the platforms core works on. Keep it in some experimental branch until it is ready and more important why would they even submit the PR if a ton of tests are failing?
If it's a compile-time switch to build v8 or Chakra and it's not impeding Node development, there's no harm.
Node is a large code base. The Chakra merge will eventually work and pass all tests - give it some time. One cannot reasonably expect such a large merge to work flawlessly out of the gate. Even the IBM PowerPC port of the V8 engine took many months to stabilize - and it's the same v8 engine.
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#79But 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.
> before you are forced to do something terrible
A little melodramatic, don't you think?
Re: Enable Node.js to Run with Microsoft's ChakraCore Engine
#80I am sure I'm a minority on this thread - but does anyone else think that if the engine is being developed in the open as open source then competition is not a good thing. I believe it's similar to having io.js and node.js - together it is a stronger platform. To this end, I think it would have made a lot of sense for MS to collaborate with webkit/blink and vice versa... that's the true spirit of open source IMO... I…
If "together" means Google is involved, I absolutely prefer the separation. Google has repeatedly screwed me over by letting their products stagnate and, sometimes, killing them off. I find it incredibly frustrating that so much of my work and digital life rely on the whims of Google.