Brainstorm with me. How plausible is it for quickcheck to break ties with rand?https://github.com/BurntSushi/quickcheck/issues/241 …
-
-
Replying to @burntsushi5
Commenting here since it's tangential, and I don't want to derail your issue, but I think we really need to decide as a community what we consider to be the norm for compiler version support. I think we can be more aggressive than other langs, but different crates have diff needs
3 replies 0 retweets 10 likes -
Replying to @sgrif
I agree. To be clear though, if it were only about MSRV, I could overlook that, at least for rand. I still like the LTS idea that boats/aturon proposed. It provides a rallying point. Adding MSRV to Cargo.toml in order to improve failure modes is also a good start.
1 reply 0 retweets 7 likes -
Replying to @burntsushi5
LTS RFC is definitely the most compelling solution I've seen so far. I also agree adding this to Cargo.toml would be great, especially if it affected version resolution
2 replies 0 retweets 5 likes -
Replying to @sgrif @burntsushi5
How’d crate maintainers be compensated ($) for maintaining an LTS version that’s no fun, only pain? There’s no plan for that, AFAICT, making the whole LTS idea accidentally anti-maintainer & pro-freeloading, despite good intentions. “Latest stable Rust only” works economically.
2 replies 1 retweet 8 likes -
Replying to @BRIAN_____ @sgrif
I don't work in crypto. I'm happy to have crypto people tell me the policy doesn't work for them. But that doesn't mean it others can't or shouldn't adopt it.
2 replies 0 retweets 0 likes -
Replying to @burntsushi5 @sgrif
I make these arguments more in favor of other open source maintainer’s interests. As soon as there is an LTS type policy, they will get bullied into doing extra free work to support it. It already happens, and they’re not in a position to say “LTS is dumb, I opt out” like I can.
2 replies 0 retweets 2 likes -
Replying to @BRIAN_____ @sgrif
I don't buy that, sorry. You could say that about a lot of stuff. I could put out code with zero docs, and people would rightfully ask me for some. Or just pass on using the code at all.
1 reply 0 retweets 0 likes -
Replying to @burntsushi5 @sgrif
I’ve lived it lots. RHEL LTS and Debian LTS policies really slowed down Firefox development for a long time. Even ignoring financials LTS makes development worse quality and slower velocity. I understand the desire to become more popular. There are better ways to win popularity.
2 replies 1 retweet 1 like
If you think this is about something as vain as popularity, then you don't understand my perspective. Twitter probably doesn't help. Probably best just to agree to disagree for now.
-
-
Replying to @burntsushi5 @sgrif
By “popularity” I’m referring to Rust’s popularity/adoption.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.