Earlier quoted context omitted.
I think it would be terrible for Rust design/evolution/policy be constrained with that kind of enterprise badness that basically bans crates.io, and crates.io is an awesomeaspect of the Rust ecosystem.
I can tell it is lots of "fun" when you can only use a Maven mirror, with approved jars. To get a jar into that mirror, a request needs to be sent to the legal team describing the license and business case use, after approval the IT team will add the said jar to the mirror. The same applies to version upgrades of already approved jars. This is a typical scenario I had already in a couple of projects.
The Rust Platform
251–256 of 256 posts
Re: The Rust Platform
#252Earlier quoted context omitted.
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.…
Rust will already allow you to have multiple versions of transitive dependencies.
I go to those pages and I am given 0 information on how the thing actually works.
Re: The Rust Platform
#253Earlier quoted context omitted.
I can tell it is lots of "fun" when you can only use a Maven mirror, with approved jars. To get a jar into that mirror, a request needs to be sent to the legal team describing the license and business case use, after approval the IT team will add the said jar to the mirror. The same applies to version upgrades of already approved jars. This is a typical scenario I had already in a couple of projects.
You willingly subject yourself to this? Why?
Re: The Rust Platform
#254Earlier quoted context omitted.
Rust will already allow you to have multiple versions of transitive dependencies.
To be honest, this is the kind of thing that would be great to highlight immediately on https://github.com/rust-lang/cargo or http://doc.crates.io/guide.html . I go to those pages and I am given 0 information on how the thing actually works.
Re: The Rust Platform
#255Earlier quoted context omitted.
You can still have a tiny install if you want to. But most people not knowing what to do will be able to have batteries included setup. Basically: people knowing will still have freedom, people not knowing will have an easier life. And in the end, in 2016, you generally don't care if you download a few extra 100Mo. If you do, you will just find spend the time to find to have a smaller setup.
> And in the end, in 2016, you generally don't care if you download a few extra 100Mo. I suggest a trip to anywhere outside the western world.
- choosing a bare bone small manual install; - making the download in advance in a place where you can or during the night;
It's not like you have less option. You just have a clear default choice.
Re: The Rust Platform
#256Earlier quoted context omitted.
You can still have a tiny install if you want to. But most people not knowing what to do will be able to have batteries included setup. Basically: people knowing will still have freedom, people not knowing will have an easier life. And in the end, in 2016, you generally don't care if you download a few extra 100Mo. If you do, you will just find spend the time to find to have a smaller setup.
So if you don't know what to do the solution is to download all the possible packages?Is there a user story/use case solved this way? The documentation for each package is available online so wouldn't make sense to actually read it before to download a package?