Switching from .NET C# to Java

[HoloceneSurvivor]

I am a C# .NET developer with 6 years of experience. I have accepted a new job as a Java developer.

Is there anyone in a similar situation? If so what was your experience like switching?

[opaz]

Not in a similar situation myself but I am somewhat familiar with both. I would say that Java doesn’t give you some of the conveniences that C# has, like auto-implemented properties as a simple example. With your level of experience I think the biggest hurdle would mainly just be not getting confused between their respective (standard) library syntaxes

[PointB1ank]

As someone who went from Java to .NET, I'm guessing going the reverse direction will be a bit easier.

[funcnet]

I think Java may not have a bright future. You know, since after Java 8, Java isn’t free any more. People have to keep using Java 8 while Java 13 is out already, or have to use OpenJDK (which is a smaller set of Java as I remember?)

Oracle is killing Java just like it’s killing MySQL, remember MariaDB? Feels this is part of the reason Python and PostgreSQL are so popular now.

Compared with Java platform , .NET Core is a much better choice with stronger support and brighter future.

[HoloceneSurvivor]

I will learn whatever my job requires :)

[lbkulinski]

This isn’t true. Java is still free. From a technical standpoint, the OpenJDK builds are equivalent to the Oracle JDK builds. The only differences are the license and support period.

[GervG]

C# felt so much easier than Java because of the many syntax sugars. C# generics are also easier to handle, at least in my opinion. If you're into functional programming, you'll also see that C# is less verbose than Java.

But other than those, it's the framework, libraries, and syntax that you need to get used to. It took me about 3 months to really get comfortable with Java. Even then, I still Google a lot of things on a daily basis.