Java libgdx or C# Unity3D?

Question

Game development

I wanted to make my own games for a very long time, but my hands didn’t reach, and now 4 months ago I started learning Java in order to learn libgdx later. I wonder if I did the right thing? After all, there is a more popular Unity engine, you can use "sharp" in it. I read somewhere that java and c# are very similar. So is it worth jumping to c# for the sake of unity, or staying on "java" for libgdx?

Answer 1

Java and Sharp are really very similar in syntax, but the internal differences are quite large. In general, you can jump with little blood.
Comparing libgdx and unity is very incorrect.
Unity is a ready-made and complete engine with ready-made utilities for it.
LibGDX is just a framework for the basic stuff. Those. render\resource system\network\base classes of the game, everything will have to be written by yourself. Utilities, as well as content storage formats, will also have to be written by yourself. The map editor will also have to be written by yourself. Another option is that many of the things described can be found already written by someone and put together.
Unity, although a powerful engine, will have to put up with the fact that it provides and not a step to the side, no matter how uncomfortable and illogical it looks.
LibGDX gives you the opportunity to write exactly the engines you need for a particular game with the necessary and convenient toolset for you.
For example, if the game is initially conceived as a platformer, then it is much more convenient to write everything specific for this game on LibGDX, most likely it will be even faster than on a unit.
If the game is something like a CS, then such a game is much easier and faster to make on Unity, but later it will be more difficult to refine for the sake of unique features and the number of crutches will grow in proportion to the number of unique features.

Answer 2

Indeed, as they say above - it all depends on the goal, if you want to understand exactly the process of writing code for the game, find out how it all works, then libGDX is well suited for this purpose. In Unity, it is more difficult to understand "how does it all work?" everything has already been done for you, but with certain efforts, the result will be approximately the same both there and there.
I started writing with libGDX, then switched to Unity as it started to gain popularity, and as it turned out, it's a cool engine! There were no problems with the transition from Java to C #, I just opened a new editor and started writing. Yes, there are some nuances and pitfalls, but Google decides everything :)
PS Now we are going to switch to another framework, because. the Unity engine is too cumbersome and clumsy for our purposes.