4 ms·
Parity yes, but documentation and support not so much. Using Java on Azure always felt like being Microsoft's red headed step child when compared to C#, and for
by DerArzt 5y ago
Parity yes, but documentation and support not so much. Using Java on Azure always felt like being Microsoft's red headed step child when compared to C#, and for good reason since C# is of course a Microsoft Language.
I don't fault Azure to much on this, but it did leave my team annoyed a lot of the time.
- pjmlp 5y agoMight be the case, however I think they do feel the pressure of Java on the backend. On my bubble it feels that .NET on UNIX has come too late, and unless one is deep into MS stack the adoption is less stellar than it could be. On polyglot shops Java based stacks tends to win over .NET ones on RFPs. Even well known names like Sitecore are now going polyglot on the backend.
- louhike 5y agoI think it depends. .NET on UNIX has allowed it to survive in some places. I don't think I would still be a .NET developer if it wouldn't have happened. It's far easier to sell .NET as a technology to upper management now than we can deploy it on Linux servers with no Windows Server licenses cost. And even though developing on .NET is fun for a lot of developers, using Windows Server is definetly not.
- pjmlp 5y agoWhile on others the rewrite required to move from .NET Framework into Core, while leaving 20 years of Windows only libraries behind has prompted several polyglot shops to jump ship. I have done two such migration projects. The reference to Sitecore was an example of one of the strongest .NET CMS on the enterprise space that now is having a portfolio based on .NET, Java and NodeJS. Microsoft always behaves as if rewrites weren't a cost center, but they are and with Core, alongside the whole desktop mess, many have reached their rewrite budget with Microsoft technologies.