3 ms·
When I started learning Rust a year ago, I thought I was going the hard route, but I was surprised how much sense it made. Especially the whole packaging thing
by atoav 8y ago
When I started learning Rust a year ago, I thought I was going the hard route, but I was surprised how much sense it made.
Especially the whole packaging thing with cargo makes so much sense. Compiling your application on a new machine is a breeze, you just need cargo and the rest happens automatically.
In the meantime I always find myself wondern how I was meant to do dependency managment again in python. Moving projects between machines can be a horror compared to Rust.
pipenv is a step forward, but nowhere near enough. We need something that just works and is part of python.
- daveFNbuck 8y agoFor larger projects, I like to use Pants [1]. You just include an installer script in your repo and anyone with a Python installation should be able to build your project on their system with a simple command. Of course, plenty of issues pop up in practice, but it works remarkably well. [1] https://www.pantsbuild.org/ https://www.pantsbuild.org/
- emj 8y agoWhen you start having multiple incompatible ABIs active at the same time, that's when dependencies get hard. You get automagical solutions that only work for some people because it's hard to see all possible combinations of versions. I think Rust is still too young.
- richardwhiuk 8y agoRust's solution is 'build everything', so you can't have incompatible ABIs. That might not scale, and it means initial build time is pretty appalling, but unlike Python, Rust compiles to a binary, so it's less manky.