3 ms·
Rust is the future of tooling [0]. While [0] is about JS tooling specifically, we're seeing the same effects in other languages as well. Turns out, you probably
by satvikpendem 4y ago
Rust is the future of tooling [0]. While [0] is about JS tooling specifically, we're seeing the same effects in other languages as well. Turns out, you probably don't want to write infrastructure tooling in slow, dynamically typed languages when faster, more safe languages exist. Python knows this already, with much of the scientific computing libraries being just wrappers over the core C++ codebases. JS is beginning to catch up as well, with swc (speedy web compiler), stc (speedy type checker), Turbopack (Webpack successor) and so on, with Vercel leading the charge mainly.
[0] https://leerob.io/blog/rust#the-future-of-javascript-tooling https://leerob.io/blog/rust#the-future-of-javascript-tooling
- nine_k 4y agoI'd say that you don't want to write the second crop of the tooling in a language like JS or Python. This is because the first crop, like mypy or babel or jslint existed, and has shown the general direction. But for the first crop, a slow-running but fast-turnaround language was essential, to my mind. The first iteration had to move fast, and change the direction fast, because it wasn't yet clear what direction was going to be right.
- Already__Taken 4y agoeven just knocking up a cli too in python I'm seeing so many cases and states I could be in that python just isn't warning me about.