3 ms·

If your end game is working professionally just check what is more in demand in your geographic location. Personal opinion C# is a lot better than Java. You h

If your end game is working professionally just check what is more in demand in your geographic location. Personal opinion C# is a lot better than Java. You have less boilerplate code (getter and setter in 2018, really?) and lambdas are great. But really both are similar so you can pretty much just start with one and still find your way in the other.

lockje 8y ago
Honestly, people still using the getter and setter argument in 2018 as a reason to pick a language should not be taken seriously. Indeed Java has more boilerplate, but honestly I've never been bothered by it (as you can generate most within your IDE) and because its explicitly written down it can make code more readable. And Java also has lambda's.
- wernercd 8y ago
  Yeah... the bigger reason to move away from Java isn't Getters and Setters... The bigger reason is one word: Oracle Whether you go towards C# or other companies... Oracle is a horrible company.
  - Accipitriform 8y ago
    Oracle is only one player in the Java ecosystem. OpenJDK owns just about everything now, and most organizations are going to get support somewhere besides Oracle. There's been some good recent innovation with Java, and I think it'll continue due to the new accelerated release schedule. That reminds me, I want to experiment some with AOT compilation and also the new GC plugins.
- jcelerier 8y ago
  > because its explicitly written down it can make code more readable. more text to read does not means "more readable", it means more effort to do
  - walljm 8y ago
    unless that text validates hidden assumptions, or conveys important information to the user. not always the case, but you can't argue that "less text is more readable" any more than you can argue "more text is more readable". what you want is, "just the right amount of text" which will depend on your tastes.
- tigershark 8y ago
  Java is much heavier to read because of all the boilerplate. And it may have lambda but for example the stream implementation sucks compared to the elegance of LINQ. They had 8 years to make it right and I’m still amazed how did they manage to implement it so badly...
- osd 8y ago
  lambda's are much more limited in flexibility when compared with linq. Because of the way java lambda's work, I imagine there are some scenarios where they are more performant, but it probably comes down to the specific problem/usage.
yawz 8y ago
Java is the most popular language of the JVM ecosystem, but not the only one. If I were to restart from scratch, I would seriously look into Kotlin, which is how Java should have been.

lockje 8y ago

Honestly, people still using the getter and setter argument in 2018 as a reason to pick a language should not be taken seriously. Indeed Java has more boilerplate, but honestly I've never been bothered by it (as you can generate most within your IDE) and because its explicitly written down it can make code more readable. And Java also has lambda's.

wernercd 8y ago
Yeah... the bigger reason to move away from Java isn't Getters and Setters... The bigger reason is one word: Oracle Whether you go towards C# or other companies... Oracle is a horrible company.
- Accipitriform 8y ago
  Oracle is only one player in the Java ecosystem. OpenJDK owns just about everything now, and most organizations are going to get support somewhere besides Oracle. There's been some good recent innovation with Java, and I think it'll continue due to the new accelerated release schedule. That reminds me, I want to experiment some with AOT compilation and also the new GC plugins.
jcelerier 8y ago
> because its explicitly written down it can make code more readable. more text to read does not means "more readable", it means more effort to do
- walljm 8y ago
  unless that text validates hidden assumptions, or conveys important information to the user. not always the case, but you can't argue that "less text is more readable" any more than you can argue "more text is more readable". what you want is, "just the right amount of text" which will depend on your tastes.
tigershark 8y ago
Java is much heavier to read because of all the boilerplate. And it may have lambda but for example the stream implementation sucks compared to the elegance of LINQ. They had 8 years to make it right and I’m still amazed how did they manage to implement it so badly...
osd 8y ago
lambda's are much more limited in flexibility when compared with linq. Because of the way java lambda's work, I imagine there are some scenarios where they are more performant, but it probably comes down to the specific problem/usage.

yawz 8y ago

Java is the most popular language of the JVM ecosystem, but not the only one. If I were to restart from scratch, I would seriously look into Kotlin, which is how Java should have been.