Rust is interesting because it occupies contentious programming languageterritory: it attempts to graft lots of semantic type information topreviously unencoded ideas of memory sharing semantics. Why? Becausedevelopers likely can't be trusted with memory management in any form.This borrow checking enforces a very consistent, cohesive style acrossRust programs; memory can only be shared in a particular fashion, whichimpacts the data flow architecture of your entire application.
Jon Blow's Entity systems and the Rust borrow checker … orsomething andIdeas about a new programming language forgames talksare essentially rants against Rust; he claims that manual memorymanagement is fine and necessary for being ergonomic, thatexception-based control flow can be useful, etc. The talks are worthskipping around throuhg on 2x speed to get the gist - they're rants,really, with a couple of legitimate nuggets of information.
Despite claims about not having a runtime, Rustdoes! Even if compiledwithout runtime, we do have some setup for generating threads and such;this is particularly necessary for allowing code to actually run onWindows systems.
This fun hack, Rust in aninstant, shows howyou can easily redefine libc functions, then link with them, in the samefile - as Rust knows to link with some C function with some name, and itcan also provide C functions with those names.
Five years of Rust - a cross-platform programming language for the nextdecad…is a huge Rust puff piece enumerating the good parts. Probably phrasedbetter than I could! But always remember that strong type systems comeat the cost of programmer brain. They're nice for serious productionwork, but not necessary for prototyping. Rewriting in Rust is good, butI'm not sure if the first draft has to be.
https://tiemoko.com/blog/blue-team-rust/: What does memory managementmean for Rust? Great take from a security perspective.
Polonius contains the algorithmthat specifies the Rust borrow checker; if you're interested in a deepdive, this is absolutely the place to start.
The Pain Of Linear Types In Rust -Faultlore is a type-theoreticinvestigation of Rust's type system, an explanation of why it is notactually linear, and elaborates on the pain that a real linear typesystem would cause in Rust.
Rust replacements for standard tools are quite popular.https://www.youtube.com/watch?app=desktop&v=A65w-qoyTYg: zero-costcopy in Rust! The Rust EmbeddedBook elaborates on methods forwriting embedded software in Rust.