4 ms·

> That should be acceptable to everyone. I used to build things with frameworks and languages with yearly upkeep requirements. > And those who prefer to live

by lugged 5y ago

> That should be acceptable to everyone. I used to build things with frameworks and languages with yearly upkeep requirements. > And those who prefer to live in rot, What rot? If my application didn't change I'm not sure why my dependencies should need to. Regarding golang, I hated go get and the go workspace idea when I first started with go. Then I got over it, now I try to use modules and I just get annoyed, the whole system is confusing and flaky. All this change is doing is pushing me further into rust. It has problems too but they tend not to do this kind of hand wringing.

Thaxll 5y ago
The change does not affect either the Go language or the way that you compile the code or fetch dependencies, what's the problem? Go is much more stable than Rust, you know how many Rust libs need nighlty to work?
- stouset 5y ago
  > Go is much more stable than Rust, you know how many Rust libs need nighlty to work? Rust libs that use nightly do so because they're opting in to new features, not because released features are unstable. Even then with the releases of const generics, proc macros, and a couple other big-ticket features, fewer and fewer Rust projects require nightly anyway.
- steveklabnik 5y ago
  How many do? Which ones? I’m curious what you’re still running into. (This is me being curious about your Rust comment, not implying anything about the relative stability of the two languages)
  - Thaxll 5y ago
    For example: https://github.com/rust-lang/rustfmt https://github.com/rust-lang/rustfmt
    - steveklabnik 5y ago
      rustfmt is not a library, and folks don’t depend on it as one. The only nightly features it uses are “hey let me use compiler as a library please,” which is also not, in my experience, common in the ecosystem. Even furthermore, it’s distributed precompiled in your rust installation, so that doesn’t end up giving you a nightly dependency to use it. Anyway, thanks. Nightly does exist to be used, but our users largely report using stable, so when people say things like this, I am trying to see if there’s any blind spots.

by lugged 5y ago

Thaxll 5y ago

The change does not affect either the Go language or the way that you compile the code or fetch dependencies, what's the problem? Go is much more stable than Rust, you know how many Rust libs need nighlty to work?

stouset 5y ago
> Go is much more stable than Rust, you know how many Rust libs need nighlty to work? Rust libs that use nightly do so because they're opting in to new features, not because released features are unstable. Even then with the releases of const generics, proc macros, and a couple other big-ticket features, fewer and fewer Rust projects require nightly anyway.
steveklabnik 5y ago
How many do? Which ones? I’m curious what you’re still running into. (This is me being curious about your Rust comment, not implying anything about the relative stability of the two languages)
- Thaxll 5y ago
  For example: https://github.com/rust-lang/rustfmt https://github.com/rust-lang/rustfmt
  - steveklabnik 5y ago
    rustfmt is not a library, and folks don’t depend on it as one. The only nightly features it uses are “hey let me use compiler as a library please,” which is also not, in my experience, common in the ecosystem. Even furthermore, it’s distributed precompiled in your rust installation, so that doesn’t end up giving you a nightly dependency to use it. Anyway, thanks. Nightly does exist to be used, but our users largely report using stable, so when people say things like this, I am trying to see if there’s any blind spots.