#RUST LANGUAGE INSTALL#
#RUST LANGUAGE PATCH#

#RUST LANGUAGE PATCH#

Fetch done by the packaging system: Applying the patch should be possible.

Network fetching by cargo: Applying it is going to be a mess but you have no reproductibility anyway so you could cheat a bit.

Now I want you to imagine that there is a patch or bump to be done on a library almost everyone uses, it will have to be applied on each dependent of the software (see previous section), which is probably going to take a very long time (like 2 weeks for a slow validation of a package maintainer and add a bit of QA testing time), there is two three ways I currently know on how Rust is packaged: Rust has a quite similar way of ending up with a pile of dependencies for a simple application.

#RUST LANGUAGE INSTALL#

In npm you often end up with way too much parts, node_modules directory in my install of mastofe has 1063 modules, this is basically the amount of stuff you get on a basic (but not minimalist) Linux system. So we end up with applications packages that are easy to spread out but difficult/impossible to maintain in the long term… I would call that a virus, good or evil. a files in C) nor source code either (instead of binaries it could be the source). Dynamic and Static Linking have both points for security and it all goes down if the system/environment is controlled or not (and any code in a broken environment is going to be broken anyway)Īdditionally as far as I know, there is also no shared location on the system for static libraries (.Static Linking isn't well integrated in packaging systems (it's more often used for a minimalist rescue system, which tends to be a completely separated system).Static Linking is great for distributing binaries on unknown systems (Netscape still runs with official static binaries today, it's hopeless with dynamic).Dynamic Linking is great for shared libraries on a managed system so you can fix something once a for all.There is only Static Linking… another thing where a lot of stuff was thrown around, my take about linking is:

I've been ranting against rust on social media from time to time and I quite want to put down why I just basically ban rust and specially consider it harmful as a system language, by that I mean stuff like libraries, as I might have to grow okay with rust for applications… (or maybe not, for now I'm ignoring update/new stuff done in rust, specially with rust as an argument) There is no system libs Rust sucks as a system language - Cyber-home of lanodan Sorry, I do not value($$$) your privacy.

Rust language