|
|
|
|
|
by ditoa
4865 days ago
|
|
Pretty much this in my experience. C# (and .NET in general) is pretty nice to work in but it is expensive from pretty much every angle. From Visual Studio (which runs over $10k for the Ultimate license) to needing the Enterprise version of Windows Server to do any kind of serious clustering you need a pretty big budget for software if you are going to commit to Windows for your production big data platform. Also a lot of big data farms have some hardcore kernel optimisations which are not as easily done on Windows (if at all). Also Java runs pretty much everywhere and is supported. C#/.NET is not (and Mono is not a decent response, if it isn't first party supported it isn't supported). |
|
Its not for C#.
Also to say that its not first party support is a little disingenuous as ultimately one would never say pick a messaging queue that implemented AMQP because it wasn't first party. C# is an ECMA standard. AFAIK the mono compiler has no issues implementing it as well as the Microsoft msbuild/csc.
For me as to why I wouldn't, its simple. Mono isn't as fast as the JRE on linux for most operations, at least I've not heard it is, and its so far removed from my interests and work to test it. http://reverseblade.blogspot.co.uk/2009/02/c-versus-c-versus... I know the mono team have done a lot over work over the last 4 years, but still. I think that is the crushing blow.
Whilst F# support, or TPL or LINQ might make development nicer, I don't think the performance concerns can be adressed.
However, C# has one big thing going for it, unlike java its never tried to install the chuffing "Ask toolbar". Oracle are going to the special hell.