4 ms·
My company uses .NET mainly so it's nice to see these libraries. But from recent experience with several of them I am starting to be a little wary of .NET SDKs.
by maxxxxx 9y ago
My company uses .NET mainly so it's nice to see these libraries. But from recent experience with several of them I am starting to be a little wary of .NET SDKs. It seems most .NET SDKs are either buggy, incomplete or have some other issues. It feels like you are a second class citizen with .NET.
I would prefer if I could call Java SDKs from .NET. These SDKs seem to be higher quality than most .NET SDKs.
C# is a great language and .NET is good but for the availability of 3rd party libraries I would probably go the Java route if I had to start from scratch.
- mattchamb 9y agonot sure i would go this route, but you can actually call java libraries from .net using a project called IKVM. I used it for a toy project and it seemed to work
- Kipters 9y agoIKVM development has been halted: http://weblog.ikvm.net/ http://weblog.ikvm.net/
- jackfoxy 9y agoDevelopment halted, yes, but AFAIK rock solid up to current Java release.
- gwenzek 9y agoSo sad to learn about that. Ikvm was so great! It was really granting you access to all the Java world in .Net I hope it will find a new developer. Microsoft should pay someone to do it IMHO
- maxxxxx 9y agoI don't understand why MS hasn't been supporting IKVM already. It makes .NET a much more viable option for many projects. There are a lot of Java libraries out there for which .NET has no equivalent or only low quality ports.