4 ms·
Weak standard lib is poor approach imo. Supply chains are real and being scared to design good API that will survive test of time sounds like poor excuse At w
by hardware2win 4y ago
Weak standard lib is poor approach imo.
Supply chains are real and being scared to design good API that will survive test of time sounds like poor excuse
At worst you could steal API design from some mature and battle tested base class libs like .net
- sbergot 4y agorust lifetimes and traits leads to different designs than .net more classical OO with managed memory & runtime. Also the rust team doesn't have Microsoft manpower. It is a bit unfair to say "just do like .net". To me the right approach is to publish an "official" meta package that depends on a few core packages that work well together.
- pharmakom 4y agoI agree that supply chain is a risk but I think you are creating a false dichotomy. There is nothing stopping us from having a small standard library and a set of official - but optional - crates for common things like regex. This is the best of both worlds in my view.
- recuter 4y agoIt is not a weak standard lib and nobody is making excuses. Your mental mapping doesn't apply here, look into how it works if you are interested as it is different from what you are used to.
- JamesSwift 4y agoYeah, from experience spinning up in Rust it is definitely not a good first-run experience. - You type something in expecting autocomplete, its not there. "Huh, thats weird" - Look it up online. Sure enough, its not in the standard library. OK, what should I use then? - Do research to figure out what 3rd party crate to use - Tend to abstract/isolate those bits in case you need to rip it out for a different implementation later