>> 100% USDA Grade-A Certified Prime BS, as shown by both projects' ages (15+, 30+ years) and maybe the definition of legacy How should 'legacy' be defined? I

>> 100% USDA Grade-A Certified Prime BS, as shown by both projects' ages (15+, 30+ years) and maybe the definition of legacy How should 'legacy' be defined? If the software is actively developed and gets new features regularly, I would not consider it legacy. If the software only gets maintenance / bug fix updates or is not updated, but is still used in production, then it is legacy software. >> I would say projects like Fuchsia and Rust itself aren't legacy because you can move fast and break things Fuchsia is not widely used (yet?). I am not sure how much "moving fast and breaking things" happens in Fuchsia. Rust has the concept of editions (https://doc.rust-lang.org/edition-guide/editions/index.html https://doc.rust-lang.org/edition-guide/editions/index.html) and spends significant effort to maintain backward compatibility. You do not have to "move fast and break things" to not be legacy.