6 ms·
I do not even see the need for justification : After LINQ and Rx and the maturing of Mono, .NET is now far ahead of the Java ecosystem, even including Scala 2.9
by _debug_ 15y ago
I do not even see the need for justification : After LINQ and Rx and the maturing of Mono, .NET is now far ahead of the Java ecosystem, even including Scala 2.9, in terms of developer productivity. The only reason I am having to learn Scala is that I am already quite familiar with the Java ecosystem (having used it at work for many years before I started doing something on my own) and do not wish to start from scratch in the .NET world.
- plastics 15y agoI am also quite familiar with the Java (and Ruby and pre iPhone Objective-C) ecosystem and invested quite a lot time in getting proficient with Scala since 2007 but recently got hooked on F#. My experience has been, that the available documentation on .Net (and F#) is so much better compared to the other stacks I know, that after three months or so of dabbling in my free time with .Net I already feel like having a much more solid base in .Net than the other platforms (where I have 4, 3 and 6 years experience). Granted this might be due to me either suck at Java, Ruby and Objective-C or me not yet having real world experience with .Net and being oblivious to ugly corner cases, warts etc. you only come across on a big real world project. But honestly my first contact with some of the books and online resources available for the .Net ecosystem and comparing that with what I was accustomed to was shocking.