3 ms·
I think rust needs to slow down in this regard. I have been with Python since 1999 and the stdlib has held it back, I have also used Scala and Haskell and have
by sitkack 10y ago
I think rust needs to slow down in this regard. I have been with Python since 1999 and the stdlib has held it back, I have also used Scala and Haskell and have witness the mess that platform libs on each have caused.
What Rust has right now is pretty amazing. What needs to happen is a way for devs to easily break the dependency cycle and include multiple versions of the same crate. Something that has plagued Haskell. I dunno what the answer is, trait only crates, struct only crates?
If people want to 'curate' (shop) a set of packages, they can make a meta package that exports its deps.
There is literally no reason to ship libs with the compiler aside from the basic verbs and nouns.
With verioned and properly name-spaced imports, one could use different curated libs.
- steveklabnik 10y agoRust will already allow you to have multiple versions of transitive dependencies.
- sitkack 10y agoThis needs to be screamed from the hill tops!
- bassislife 10y agoWhich I guess is normal since it does not create any dependency cycle. A new version might as well be thought as a completely different package (of perhaps similar functionality).
- wilmoore 10y agoTo be honest, this is the kind of thing that would be great to highlight immediately on https://github.com/rust-lang/cargo https://github.com/rust-lang/cargo or http://doc.crates.io/guide.html http://doc.crates.io/guide.html. I go to those pages and I am given 0 information on how the thing actually works.
- steveklabnik 10y agoCargo's docs need a bunch of work, it's true. I have so much to do :(
- goodplay 10y agoIf you can, could you elaborate more on python's stdlib holding it back? I think batteries-included experience is one of the reasons why so many people (including myself) use python. It's also one of the features I sorely miss when using Rust. Luckily, Rust's stdlib is starting to tend towards being more practical with recent additions like system time.
- sitkack 10y agoThe 'std lib is where libraries go to die' was invented by Python. The libs are shallow, don't break backwards compat and provide a substandard experience. Things that continue to improve provide an out of tree alternative package name. Python codebases that are resilient don't use much of "core", arrow for time, requests for http, simplejson, etc. Using core is an antipattern that will get you stuck on a version of the language which is ridiculous. Linking the language and the libraries together is a mistake.
- glandium 10y agoPlus, python's std lib is a mumbo jumbo of all sorts, there is no API coherence.
- oblio 10y agoThat's a failure at the moment of inclusion. I'm guessing it was done for convenience and to increase adoption (getting decent libraries in the standard library faster).
- _ZeD_ 10y agoJust as a data point... I like and heavily use the core libs... And not once i used arrow, request or simplejson, while knowing them, because i didn't feel the needs
- the_mitsuhiko 10y agoThen you most likely have various security or logic problems in your application unfortunately.
- anamoulous 10y agoOne of the things I love above all about Python and Ruby are the kitchen-sink standard libraries. The node ecosystem is deeply frustrating in this respect.
- krylon 10y agoIt has been a while since I did anything with Python, but I did like its standard library. It was reasonably comprehensive without feeling bloated, and the documentation was pretty good (mostly). Having a good standard library also makes deployment easier. (In Go, OTOH, I tend to care less, even though its standard library is quite good, because thanks to static linking, deployment is always easy, no matter how many third-party libraries I use.)
- deleted 10y ago[deleted]