4 ms·
How about Obj-C that eliminates all of the memory alloc/dealloc and runs in the JVM? ;) Ok, that sounds just awful as I doubt much would port well. But, it does
by devmonk 16y ago
How about Obj-C that eliminates all of the memory alloc/dealloc and runs in the JVM? ;) Ok, that sounds just awful as I doubt much would port well. But, it doesn't seem to make any sense to reinvent the wheel. Recent JVMs handle garbage collection fairly well.
How about ditching all of the Obj-C and rewriting Cocoa (for OS X and iOS) in Java? Easier said than done.
I say just embrace the fact that everything in OS X/iOS today is using a somewhat fast but somewhat archaic language, and just make XCode better able to spot memory leaks in code.
- scrod 16y agoIt's (mostly) already been done — Apple called it the Cocoa-Java bridge: http://cocoadevcentral.com/articles/000024.php http://cocoadevcentral.com/articles/000024.php It became officially deprecated about five years ago, but quite a few important apps used it, Cyberduck (http://cyberduck.ch/ http://cyberduck.ch/) being one of them.