-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a branch for 0.6.x? #324
Comments
As of #325, the Rust+Wasm is another 3x faster. See http://fitzgeraldnick.com/2018/02/26/speed-without-wizardry.html for details. |
Hey @fitzgen, That's great - and I look forward to using it myself. But there are a lot of projects out there who will be relying on the 0.6 series for the next ~1 year until Node.js 6 is out of support. It would be great it those projects could benefit from the work already done by @mraleph. I'm not at all advocating to abandon the WASM efforts, but the wider Node.js ecosystem is not ready to drop support for Node.js 6. |
I ported optimizations from the article into https://github.com/7rulnik/source-map-js |
I read @mraleph's blog post about optimizing source-map parsing without WASM earlier this morning. Since 0.6.x will be used for a long time in the Node.js ecosystem.
I'd love to apply some of his lessons to the code base. Would you be open to creating a 0.6.x branch to send pull requests against and eventually releasing a 0.6.2?
The text was updated successfully, but these errors were encountered: