4 ms·
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 JITl
by mattkrea 11y ago
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.
- morebetterer 11y agoAs 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?
- mattkrea 11y agoIt 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?
- morebetterer 11y agoIf 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.