Is it difficult to migrate from Java to C#?

Question

Java

I am currently learning Java, but some kind of professional (student) burnout and I want to do something and not just read a textbook, and I decided to do something on Unity, but C # scripts are written there, is it difficult to switch from JAVA (I'm going to learn it , and not going to stop) to C# ?

Answer 1

The differences in syntax are small things compared to the huge ecosystems around each of these platforms. And each with its own approaches, libraries, etc.
That's when you start to delve into programming, the problems of different syntax will seem negligible. Understanding the syntax is a matter of one week. And to delve into the platform, it all depends on your experience. So learn now what you like, all the same, the achievements will not be wasted.

Answer 2

As for the language, there are many similarities as well as differences. First of all, in C#, in the vast majority of cases, automatic properties are used instead of getters/setters, and in C#, you have to master the TPL library (async/await , IAsyncResult , Parallel.Foreach() ... etc), which contains a lot of syntactic sugar for creating multi-threaded applications, and the LINQ / PLINQ (Parallel LINQ) language which is used to create queries against collections, XML-cams and Relational databases. In C #, unlike java, to implement events delegates (Event) are used instead of instances of handlers, also anonymous methods are used to implement lambda expressions in C # and there are no functional interfaces. As for the .NET platform itself, you have an exciting path to explore the bowels of the CLR andDLR .

Answer 3

somewhere in a week I switched from java to seasharp from nothing to do

Answer 4

Not difficult, but why, when there is libGDX ? Yes, this framework is unlikely to be better than Unity, but do you really need to learn another PL for Unity?

Answer 5

no, the syntax is very similar

Answer 6

No, it's not difficult, it's the same everywhere.
and generally follow the concepts, approaches, and not the specific implementation in the framework.
they are very similar everywhere, knowing the approaches and principles, you can easily switch from one framework / ecosystem to another.
although migrating to the Microsoft ecosystem is a very dubious pleasure)