[lmickh]

Curious to hear about these .Net Enterprise devs that are not using RDBMS. It is still very much the status quo even with services like Azure DocumentDB around.

When you get a list of solid points about why Java won't be displaced and the response is watch this space, it reminds me of the folks saying "this is the year of the Linux desktop" without pointing to actual improvements coming to life.

The "new" .Net CLR really only has a compelling story if you are already a .Net shop. Nothing in the new Core and Standard implementations gives you something new if you are outside of it.

[nbevans]

There are non-legacy non-mainframey modern RDBMS you know!

Hopefully I don't need to point out the very well publicised and ongoing efforts to revamp the .NET CLR and peripheral items to run on non-Windows systems.

[lmickh]

I see. You are just commenting on the mainframe portion of the prior response.

The efforts to revamp .Net CLR to run on non-Windows systems is of little value to shops that are not already running .Net CLR. At best it is removing a negative for running .Net CLR. There is no net gain for a Rails or JVM shop for example.

The gain is only for shops that already paying the Windows tax to get .Net.

[pjmlp]

Oracle and SQL Server ADO.NET drivers still don't work on .NET Core.

[nbevans]

https://blogs.msdn.microsoft.com/dotnet/2016/11/09/net-core-... ?

[pjmlp]

I don't see ODP.NET on that list.

As for SQL Server, it is better than last time I checked. Do you have data about production loads on GNU/Linux?