5 ms·
This is one of the most ridiculous RIIR I've seen. It's a CLI tool that makes API calls. I'd bet my bottom dollar that the performance difference between API-w
by gavinray 1y ago
This is one of the most ridiculous RIIR I've seen.
It's a CLI tool that makes API calls. I'd bet my bottom dollar that the performance difference between API-wrapping CLI tools in something like Ruby/Python vs Rust/C++ is negligible in perceived experience.
If they wanted people to not have a dependency on Node pre-installed, they could have shipped Single Executable Application's [0] or used a similar tool for producing binaries.
Or used Deno/Bun's native binary packaging.
[0] - https://nodejs.org/api/single-executable-applications.html https://nodejs.org/api/single-executable-applications.html
- franga2000 1y agoHaving the CLI self-contained and easy to cross-compile is a huge improvement, as is the binary size (from what I've seen, wrapped Node binaries are huge). Also, a CLI tool should have low latency and no matter how good your engine is, an interpreter will have much higher startup latency than a proper binary.
- ramoz 1y agoIt's not just API calls though. It's often parallel processing of I/O (network, filesystem) and computational tasks like testing and compiling code.
- yahoozoo 1y agoThese tools just run the test/compile commands in a shell…