3 ms·
I'm always happy to hear about performance improvements to JS dev tooling. In recent years significant improvements have already been made, but it's still... sl
by Cu3PO42 5y ago
I'm always happy to hear about performance improvements to JS dev tooling. In recent years significant improvements have already been made, but it's still... slow.
However, I have concerns about using Rust here. Not because it's Rust specifically, but because it means yet another native dependency. I've done my best to eliminate any native code from projects because they would always cause problems sooner or later. Mostly later when coming back to an old project. Are there any plans to optionally ship the compiler as WASM to avoid this?
- tanaypingalkar 5y agoWhy you have concerns with native dependencies, it is just a transpiler and a dev dependencies. How it affect your project?
- Cu3PO42 5y agoIt affects me and other people working on it. I have to make sure the systems running the dependencies have an appropriate Python and C(++) toolchain installed. If they use Node bindings, they will probably need to be updated for newer versions of Node. When I come back to the project after some time, the first thing I need to do is update dependencies. I often had colleagues on whose devices some dependency would just refuse to compile for one reason or another. Sure, this isn't the greatest problem in the Node ecosystem right now, but it's painful enough that I would rather not deal with it.
- devongovett 5y agoWe will have a WASM build, yes. Mainly for running in the browser or on platforms we don't build for. In our tests so far, it is significantly slower though (e.g. ~30%) so it's a tradeoff.
- Cu3PO42 5y agoThat's great to hear! I might be willing to take that penalty depending on the size of the project to avoid any future incompatibilities.