- Manual memory management vs garbage collector
- Pointers vs references
- No security vs security (class loaders, etc..)
- No native threads support vs native threads
- No architecture abstraction vs WORA
Advertising
I agree but there are some 'solutions' to some of these, I remember finding a library which could take care of memory management, well actually I know nothing about anything else you listedm0skit0 wrote:Well Xian Nox made the points. Just one more thing: C++ (and C) is WAY harder to code properly with than Java.
We're talking about 1983 vs 1995. And yes, of course C/C++ is faster, but this comes with a price: portability.
- Manual memory management vs garbage collector
- Pointers vs references
- No security vs security (class loaders, etc..)
- No native threads support vs native threads
- No architecture abstraction vs WORA
Kind of missed my whole point here. Hard work is justified always. Learning it the hard way makes many other things easier as its more practical. Sometimes one must learn the old fashioned way before they learn the shortcuts like in mathematics, no? (When i say old-fashioned dont take it literal)m0skit0 wrote:Well Xian Nox made the points. Just one more thing: C++ (and C) is WAY harder to code properly with than Java.
We're kind of jumping the gun. You cant expect a beginner coder to know proper coding ethics such as bad coding structure or unoptimized code.Xian Nox wrote:Uh huh. Then let me just say one thing: neither Java, nor any other interpreted language saves you from writing bad or unoptimized code.
Not quite the argument because minecraft is a commercial and very successful game. Of course there will always be tweaks required but even at the commercial level such tweaking, and optimized code can be only practically imaginable.Xian Nox wrote:Minecraft will run on a potato if you get the tweaks.