Open Sourcing the Microsoft JDBC Driver and Maven Support

Open Sourcing the Microsoft JDBC Driver and Maven Support
blogs.msdn.microsoft.com

I would have figured microsoft would have used a linter to fix style issues with their code before Open Sourcing. E.x: https://github.com/Microsoft/mssql-jdbc/blob/master/src/main...

Anyone know if microsoft is going to specify their java style guide.

I'm sure that they'd appreciate help in cleaning it up.

How is .NET Core peripheral software? If anything it enables developers with C# codebases to move away from Microsoft's commercial products.

Having dealt with many database drivers over the years, I can say first hand that closed source drivers are the bane of my existence. The only thing worse than running into a deep-in-the-stack bug in a database driver is one that you can't correct, let alone debug properly.

Regardless of your views on closed source software on the server side of things, it's a disservice to your customers to not have open source client side drivers. The secret sauce is always on the server side so it doesn't buy you anything. At best there's (very poor) argument for security through obscurity or you're doing something silly like hiding server side features behind client side feature flags.

Plus the more tech savvy of your users will directly contribute back to improve the driver. This is both for fixing existing bugs and adding features to support existing database server features. In this particular case, I've got a laundry list of things I'd like corrected / added / improved in the SQL Server JDBC driver. Had it been open sourced a few years back, I would have already done them myself.

Unless there's a legal restriction for not doing so, like say not owning the original source, there's no good reason not to open source the client side of things.