C# or Java? What's more marketable and versatile?

Also what does /prog/ think of Haskell?

You probably need to know both anywayz, its not that hard to learn one, when you know the other. I need both to do my job

C# is easier to start with imo but considering they're both .Net chances are you will eventually need to know both.
You can wrap the two together incredibly easy so if you're doing open source projects it's handy to know both so you can take contributions in both java and C# without any complications.

java is probably the more viable of the two
ive seen many c# guys have to rotate certs or accept secondments, few java guys with the same troubles.
im a hardware guy myself, working toward CCIE.would rather eat dicks than code, thats no career unless you're running your own firm.

>>1
Loving the functional programming. Haskell, Conjure, Scheme, Scala, etc

In Java vs C# I'd say its more of a preference. I like Java more but they are very similar so its quite easy to change over.

you'll make more money if you learn the .NET framework. besides that the languages are basically the same. I prefer c#

personally more of a fan of java

IT intern this summer, no idea what I'll be using

started Haskell recently
basics are uber easy to pick up with other programming knowledge

C# is dead. Even microsoft killed it internally and now opensources .net in naive attempt to buy harts of hackers.
Java is quite gay language, but still alive and well.

Java. Especially if you're looking at functional programming. Scala runs on the JVM and it interoperates with Java. All the benefits of functional and OOP, and you can use the HUGE amount of open source Java libraries.

Also, you don't have to deal with .net. BONUS

C# and Java are basically interchangable except for the way their respective libraries/frameworks look like.

I would say Java is hotter on a front-end (small) business standpoint, C# is more for a somewhat more professional (back-end) application wise.

Honestly though, just pick one and learn it. the second one will be peanuts to pick up once youve mastered the other.

>>8
c# isnt dead lmao

>>11
technically, while last amateur basement dwellers that use it are still alive, c# isn't dead.
but for the world it is dead, killed by microsoft themselves.
useless and slow crap, that cannot even match java - and unlike java, it is not even portable. rubbish by design.
used by novice coders who cannot into real programming languages.

C# is for cut rate Indian programmers. Learn Java. Startups use JVM languages a lot more than C#.

>>10

C# is more for a somewhat more professional (back-end) application wise

This isn't true. Sure, C# is widely used in industry, but so is Java. I've worked for a major online supermarket, done a couple of finance contracts, and now I freelance. I've always used Java / JVM stuff for the back-end. You tend to end up with a bit more legacy work with C#, which is always fucking terrible to maintain.

MFW when I've moved to Scala and the freelance rate is fucking high
MFW I have no face

What most people would call "learning the language", is very easy for either and trivial if you already know one on pretty much any programming language. The difference is in learning the frameworks and also the various conventions used in each framework/language.

Both languages have good demand in the job market. I'd say it depends if you like to work on open source stack or Microsoft stack. Open source is free. Microsoft has more mature tools, help, support, etc.

>>8
this. c# was created only to replace java so that Linux does not get portable applications easily. plan failed, java ecosystem is still alive. c# was killed by microsoft after it failed to create its own ecosystem.
>>11
it is dead. face it.
or cry more, your choice
it won't change the fact that you have wasted your time learning it
everybody was warning you, remember?

>>13

C# is widely used in industry

C# WAS somewhat widely used in industry
now it is dying in industry, c# programmers are only needed for maintenance of dying systems written by blind idiots

I gave up on Java years ago and moved to Ruby. Way too much boilerplate crap in java. However your choice of tools impacts the types of places you will work. For instance usually ruby developers end up in small shops, while java is used by mid tier businesses

I work in an international IT business. What I can say is we have Java programmers and C# programmers. (also some COBOL, scala and several others), you can learn either one, it's not really that hard to make the switch.

Developer here. Go for C#. If you don't need to write for android, java is dead. It's an obsolete language. And this year will be a big boost for C#. Also C# works on mobile/desktop/enterprise too - we're not in the 2000s

Java way more popular and widespread.
Android apps are Java too.
Go for Java.
Haskell is interesting to learn but I went for OCaml when I learned functional programming.