Write once, run everywhere [spoiler]slow as shit[/spoiler]
>>58569882
WRITE ONCE DEBUG EVERYWHERE
https://benchmarksgame.alioth.debian.org/u64q/java.html
>>58569882
CPU usage: 100% +
>>58569882
prove it fag
Learn one, do everything.
[spoiler]with more difficulty[/spoiler]
Can you believe that php-gtk exists?
>>58569908
When was the last time you saw a resource critical game/3D rendering software runs on Java?
>>58569904
https://benchmarksgame.alioth.debian.org/u64q/compare.php?lang=java&lang2=csharpcore
>>58569974
XD
If linux is written mostly on C, why is android using Java?
>>58569974
Literally the most popular game in the Sol system was built in Java.
A JVM client like Minecraft is pretty rare, but many, many backends for the biggest games in the world (LoL, Overwatch, etc) run on the JVM, whether or not they were actually written in Java. The JVM has hauled ass since NIO and Hotspot and is competitive with C even in tight loops.
>>58570275
Google had a lot of people experienced in writing Java and they made a decision to write android in it.
>>58570275
Because they want to compile once and run everywhere.
>>58570279
>Overwatch server-side is Java
The actual game backend and not some irrelevant web services? I'd like to see some proofs.
>>58570291
t. Retard
>>58570309
What are you calling the "actual" backend? The simulation itself is probably built in C++ alongside the client, but that isn't the interesting computational problem on a service like that. The hard part is sharing state across a distributed system, and no one builds that shit in C/++ anymore.
>>58570367
No, the interesting part is simulating the game and responding to clients with high latency. Interacting with database to store statistics is not an interesting part.
>>58570482
If you think Riot's engineering challenges are netcode and the rest is "storing statistics", I'm sorry you feel that way.
>>58570279
>Literally the most popular game in the Sol system was built in Java
I don't think the original Tetris was developed in Java...
>>58570522
I explicitly mentioned Overwatch.
>>58570522
Eat shit code monkey
>>58570529
Honest question: which one do you think is more latency-sensitive?
>>58570557
I don't get your question. Latency-sensitive is game simulation. It is done on one server. There's nothing distributed and no need for any coordination. Game simulation is not written in Java. After the game is over and simulation is finished, some results of it are stored in a database, which is a third party product not written in Java. This process is not latency sensitive at all. Before the new game starts, there is matchmaking. I believe matchmaking also is done on a single server after receiving a rather large set relevant fields from the database (but if you have evidence pointing to otherwise, please feel free to post it). When matchmaking is done, it sends results to relevant players and a single server that will host the game. So, yes, out of all described tasks, game simulation is the only one that really required low latency.
>>58570608
I'm still waiting for your response, anon.
>>58570819
You should address his concern in his response, or are these funny things called letters confusing you?
>>58570991
It's q misquote. I'm waiting for other anon's response. Here:
>>58570557
I'm waiting for your response.
>>58570275
https://www.quora.com/Why-are-Android-apps-written-in-Java-but-the-OS-is-written-in-C++
Basically, people are incompetent to learn C++ and java was already used on dumbphones.
>>58570164
>>58570279
>shitecraft
I said resource critical, not POS games that even 2004 pentium I is able to run.
Give me examples like Destiny, Crysis 3, Autodesk Maya etc