Because in theory you know what the server is running on, and can optimise for that with C++, while supporting the front end on multiple architectures using one codename with Java.
The JIT compiler of Java does the optimization you’re talking about. So that advantage of C++ is not really there.
You can compile C++ for all architectures you want as well. The reason you don’t normally use Java for clients is that the garbage collector runs at undefined times, causing stuttering. This has been rectified through new algorithms though, so the real reason why you don’t wanna use Java is because it simply doesn’t have the best tooling and libraries that C++ has, no Unreal engine and no Godot.
Why the fuck would you go for Backend in C++ and frontend in Java 🤣 just the wrong way around
1999 was rough I guess 😜
Because in theory you know what the server is running on, and can optimise for that with C++, while supporting the front end on multiple architectures using one codename with Java.
The JIT compiler of Java does the optimization you’re talking about. So that advantage of C++ is not really there.
You can compile C++ for all architectures you want as well. The reason you don’t normally use Java for clients is that the garbage collector runs at undefined times, causing stuttering. This has been rectified through new algorithms though, so the real reason why you don’t wanna use Java is because it simply doesn’t have the best tooling and libraries that C++ has, no Unreal engine and no Godot.
This is a game from the 90s my dude. Java was “The portable language”.