3 ms·
Most people won't touch .NET because the only deployment option outside of Windows is Mono, which depending on your use cases (for server software) ranges from
by jen20 11y ago
Most people won't touch .NET because the only deployment option outside of Windows is Mono, which depending on your use cases (for server software) ranges from "barely works" at best to "not even compiling your code using mcs" at worst.
Unless you start with Mono and port to .NET, you may as well forget it, and even though the runtime has the _potential_ to be nicer because of proper generics and value types and many other things, outside of Windows this is just not the case right now. Core CLR (or whatever it is called today) may fix this in future, but if you need to ship now or in the next year it is a poor bet.
- rubber_duck 11y agoASP.NET MVC 6 is RC and pretty close to stable and will support cross platform CoreCLR out of the box - Microaoft will probably start offering Linux packages with it on Azure when it's released. But even if you need something right now and CoreCLR doesn't cut it Mono compatibility story got a lot better because they could just take stuff from CoreCLR and other OSS drops from Microsoft recently - so I would say cross platform developmebt with .NET is much less painfull than it was even 2 years ago. Even more JetBrains is working on a C# IDE so you won't be stuck with MonoDevelop/VS code on non widows platforms. I'm thinking most of this will be out during BUILD. Last few posts here make me sound like a .NET advocate :D For the last year I've been doing C++/Python/Dart/JavaScript. I also used Clojure/JVM before - I'm not one of those "full stack .NET" developers - I just had great expiriences developing on the .NET platform, been keeping an eye on the ecosystem and I hate when people dismiss it on false assumptions - there is some top of the line stuff in that platform that would make my life as a developer better on a daily basis.