They built the postgres plugin in a way that nobody could usefully contribute to unless they worked at msft - like the rest of ADS the level of control they tried to maintain meant nobody wanted to work on it.
That is seemingly true of a bunch of tools. I am using an official Microsoft Python library - the repo is public on GitHub, but all of the CI or other backend integration is behind the Microsoft curtain, so it is impossible for the public to actually participate. The cherry on top is that the team that used to support the tool was impacted, so now nobody can maintain the thing.
I am curious: Which library?
The SQL Server driver for Django. Originally maintained by someone from Nebraska, Microsoft then took ownership of the project (now lives under the Microsoft GH organization). The last commit was 11 months ago. Has not supported a current release of Django for over a year now. There are almost certainly security implications for sticking on the now deprecated Django 5.0. The issues are begging for anyone at Microsoft to do something. Several pull requests sitting there with the ostensibly required updates to make it compatible with the latest Django LTS.
You can find workarounds, but it is an awful situation. Now the community is probably going to have to re-fork the library back to the public for maintenance.
I am clearly not a bean counter, but if Microsoft wants its database to win against the free options, they could do their best to ensure popular libraries can seamlessly connect.
https://github.com/microsoft/mssql-django/issues/418#issueco...
Microsoft also loves to sideline some author so some PM can say "look at this OSS project we now control!!!!" and then add controls and processes that nobody gets to even know about except for MSFT and then weird, inevitably a few years later its just a disaster area.