> If the dotnet ecosystem runs like Perl, where future versions almost always support old code with high fidelity and low stress, maybe that's fine. If the dotnet ecosystem runs like Python, where future versions are guaranteed to break existing code, such short lifespans might discourage adoption.
Although there are breaking changes [1] between major versions, in my experience upgrading .NET versions is in most cases a very straight forward experience. All breaking changes are documented and there exist a recommended action to resolve conflicts that may arise from the change. Additionally the .NET community is already used to these kind of lifespans and upgrading regularly. Samir will respond to the other concerns you voiced in you comment. [1] https://learn.microsoft.com/en- us/dotnet/core/compatibility/breaking-changes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2134482 Title: [MIR] dotnet10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet10/+bug/2134482/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
