5 ms·

I don't want my tools to break from under me, and I don't want to be forced to call tech support needlessly. Do you love dealing with refrigerator repairs? Why

• zxzax 5y ago
  It's not needless if you've found an actual bug, i.e. if your refrigerator is actually broken. I too wish it was possible to get a refrigerator that never breaks or malfunctions or needs to be replaced. If you know how to make one of those, please start selling it, you'll probably get very rich.
  • ferdowsi 5y ago
    Experiencing backwards compatibility breakages is not "finding a bug" it is the tool being broken from under you. I don't have to prepare for the possibility of having live tech support open whenever I update the Go binary in my projects. Rust advocates should not try to suggest this is reasonable.
    • ChrisSD 5y ago
      If you use highly unstable, nightly only, Rust features then experiencing breakage is almost a certainty. That's why they're highly unstable, nightly only, features.
    • zxzax 5y ago
      I think the Go team would also appreciate it if you filed bugs after finding a legitimate regression.
    • seoaeu 5y ago
      A software bug is an error, flaw or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways. If the Rust compiler developers intend to provide backwards compatibility, but accidentally make a change that breaks that, then that is absolutely 100% a bug. You are allowed to prefer that the software you use has minimal bugs, but you are deluding yourself if you think that the Go compiler (or essentially any other piece of software) is bug free.