3 points | by SBArbeit 9 hours ago ago
2 comments
This SDK is widely trusted, but it carries significant technical debt:
Performance risks Memory leaks Design flaws Maintainability issues
Which version of the .NET SDK did you review: v3 or v4?
Also, why not create an issue or maybe just a discussion in the .NET SDK GitHub repository ( https://github.com/aws/aws-sdk-net ) for the IDisposable problems you mentioned? There is definitely awareness that there are problems in the vast codebase (e.g. https://github.com/aws/aws-sdk-net/discussions/2559#discussi... )... calling out specific problems might actually lead to a fix.
This SDK is widely trusted, but it carries significant technical debt:
Popularity does not equal quality.Which version of the .NET SDK did you review: v3 or v4?
Also, why not create an issue or maybe just a discussion in the .NET SDK GitHub repository ( https://github.com/aws/aws-sdk-net ) for the IDisposable problems you mentioned? There is definitely awareness that there are problems in the vast codebase (e.g. https://github.com/aws/aws-sdk-net/discussions/2559#discussi... )... calling out specific problems might actually lead to a fix.