3 ms·
The article is wrong, the advantage of bytecode is not portability; but memory allocation, failure handling and dynamic classloading. A Java SE process never cr
by bullen 8y ago
The article is wrong, the advantage of bytecode is not portability; but memory allocation, failure handling and dynamic classloading. A Java SE process never crashes unless you leak memory, which is super easy to avoid and profile with a heap dump, so you can sleep when you release code on servers. That's the real reason for Java's success. I would never code C for servers. And if I code for a hydroelectric dam, I would use Java SE! Not kidding!
- astrange 8y agoJava is not really safe from mistakes, if you type the wrong code you will still get the wrong program. Even for 90s programming systems I recommend you try Erlang.
- bullen 8y agoErlang is single threaded, I would never use Erlang on multi core processors, ie. I would never use Erlang period! If you downvoted because Java is not safe from mistakes (duh), I suggest you try using C/C++ just for fun. If you use C/C++ on server systems for salary you will burn out.