3 ms·
So .. like ... Why not dump python entirely if you are doing a python to rust port of a core aspect of python tool gain?
by AtlasBarfed 3y ago
So .. like ... Why not dump python entirely if you are doing a python to rust port of a core aspect of python tool gain?
- Ar-Curunir 3y agoChanging your build tool to another tool (designed to be a drop-in replacement) is very different from changing your entire codebase...
- thorncorona 3y agoexisting code? swapping build tools is extremely different
- darby_eight 3y agoThere are obvious answers.... Why do you ask?
- datascienced 3y agoWell because best tool for the job. There is no natural law that everything must be bootstrapped. Languages use LLVM for example.
- eternityforest 3y agoBootstrapping is such an odd concept. Like, something that's self propagating is in a sense not fully reproducible and holonomic, unless you maintain the original non-bootstrapped version which would add tons of work. A compiler bug could put a bug in the compiler and propagate itself indefinitely. An implementation in some other languages that has an implementation in C means you could theoretically start from ASM and rebuild.
- porphyra 3y agobecause writing python is a lot easier for most people than writing rust but changing from pip to uv is like a one liner?
- tedivm 3y agoPython from the start has always been willing to use other languages and tools if it made sense. It's a pretty common pattern (at least in the data science and research circles I've been in) to write the original in python to see if it works, and then to port it over to a lower level language (C, Rust more and more these days) and expose an interface to it in Python. For things like dependency resolution, where you're doing a lot of heavy CPU operations, there is a lot of room for optimization in lower level languages.