3 ms·

Both are too young to have it evaluated fairly. It is easy to be backwards compatible on a short term.

• kramerger 3y ago
  Not really. Rust have had backward compatibility problems already during its young life. Why do you think you need to specify release and nightly to successfully build some projects?
  • masklinn 3y ago
    Because the project is using nightly features? Which are specifically not guaranteed to remain or be stabilised? That’s like complaining that the exp packages are not stable.
  • eptcyka 3y ago
    It's never backwards compatibility, its that a lot of code depends on features that are not present in older releases.
  • stusmall 3y ago
    That is because features might be feature complete and usable, but not consider stable yet and thus not part of stable builds. This because rust takes backwards compatibility seriously, it isn't an example of it breaking it.
• kiitos 3y ago
  Go is more than 10 years old, that's certainly old enough.