4 ms·
This long lifecycle is a double-edged sword between stability & features, but you can grind down one of those edges with enough discipline on backwards compatib
by bob1029 5y ago
This long lifecycle is a double-edged sword between stability & features, but you can grind down one of those edges with enough discipline on backwards compatibility.
One compelling example could be the direction MS has started to take w/ .NET Core/5/6+:
- Submit issue/PR on the dotnet/aspnetcore repo on GH (anyone can do this).
- Conversation starts almost immediately.
- Suggested changes could be merged in a matter of weeks.
- Expect your changes to become available in an official release in under a year. Pre-release builds much sooner than that.
- Expect an LTS release the following year.
I have personally experienced this workflow a few times. It is incredible to have this type of feedback loop with something that has historically been a total black box of proprietary decisions.
There are still a ton of places where you don't have much leverage, but the fact that there is any movement possible from the community at all is incredible to me (again, from a historical perspective around Microsoft & .NET).
I don't have to learn how to draft a PhD thesis in order to add value to the ecosystem. Ideas should not be filtered so harshly in my opinion.