3 ms·

Besides Node.js the main competitor is is Java/JVM. C# is a bit nicer than Java, but you can use Kotlin or Scala on the JVM. All in all I see no real advantage

Besides Node.js the main competitor is is Java/JVM. C# is a bit nicer than Java, but you can use Kotlin or Scala on the JVM. All in all I see no real advantage over the JVM/Java world - more of the other way around, since the .Net ecoystem is not as big as the JVM ecosystem. However competition is always good.

deleted 8y ago
[deleted]
jbergens 8y ago
It depends on how much better you think C# is but I think of this the other way around. You don't have to use Java anymore to get cross platform support, good performance and a stable and statically typed language. Regarding things that might be better I think the linq support in dotnets collections is better than the streams support in java since java has kept more old collection libraries.
marxama 8y ago
I've worked a lot with both C# and Java, and C# is so superior I never want to touch Java again. Especially since around C# 3.5, the distance between Java and C# has grown enormous. The two benefits I can see with Java is that it's a smaller language (easier to train junior engineers), and yes, the huge amounts of libraries. Kotlin/Scala/Clojure are nice, but my experience is that just because an organization is working with Java, you shouldn't count on being able to work with some other JVM language. At my current job, we've been forced to give up on Clojure (a language I love) because the higher-ups have decided we should stick to Java. I really hope especially Kotlin will gain more traction in the coming years, but in the meanwhile there is at least an order of magnitude more jobs in C# (where I live).
- jgalentine007 8y ago
  I hate dealing with checked exceptions in java.
nestorD 8y ago
> C# is a bit nicer than Java, but you can use Kotlin or Scala on the JVM. With .Net you get F#
- mr_overalls 8y ago
  This needs to be brought up more. It's a huge bonus. F# is fantastic.
city41 8y ago
I recently scraped some job sites in various major metropolis areas in the US and aggregated the keywords I found. There was about 5 Java jobs for every one .NET job. .NET and C#/F# are pleasant and I wouldn't be opposed to going back to them, but job-wise it seems safer to stick with tried and true Java.

deleted 8y ago

[deleted]

jbergens 8y ago

It depends on how much better you think C# is but I think of this the other way around. You don't have to use Java anymore to get cross platform support, good performance and a stable and statically typed language. Regarding things that might be better I think the linq support in dotnets collections is better than the streams support in java since java has kept more old collection libraries.

marxama 8y ago

I've worked a lot with both C# and Java, and C# is so superior I never want to touch Java again. Especially since around C# 3.5, the distance between Java and C# has grown enormous. The two benefits I can see with Java is that it's a smaller language (easier to train junior engineers), and yes, the huge amounts of libraries. Kotlin/Scala/Clojure are nice, but my experience is that just because an organization is working with Java, you shouldn't count on being able to work with some other JVM language. At my current job, we've been forced to give up on Clojure (a language I love) because the higher-ups have decided we should stick to Java. I really hope especially Kotlin will gain more traction in the coming years, but in the meanwhile there is at least an order of magnitude more jobs in C# (where I live).

jgalentine007 8y ago
I hate dealing with checked exceptions in java.

nestorD 8y ago

> C# is a bit nicer than Java, but you can use Kotlin or Scala on the JVM. With .Net you get F#

mr_overalls 8y ago
This needs to be brought up more. It's a huge bonus. F# is fantastic.

city41 8y ago

I recently scraped some job sites in various major metropolis areas in the US and aggregated the keywords I found. There was about 5 Java jobs for every one .NET job. .NET and C#/F# are pleasant and I wouldn't be opposed to going back to them, but job-wise it seems safer to stick with tried and true Java.