I understand some of the reasons for Google picking Java, but I still didn't like it. And I'm no fan of Oracle or its ilk. What I'd like to see is a phone/tablet mobile OS plus application framework based on C/C++. One thing I've missed on Android is the difficulty of porting C/C++ *IX code (the real standard) to Java. I think this is a huge loss to android to lose ~40 years of *IX continuity and the apps show it. If you like interpreted languages, great, use or write a C++ interpreter. If you like bytecode, fine, write a C++ bytecode framework. If you like JIT compilation, find, do that for C++, wouldn't be that hard. If you like fast native compiled code, C/C++ is the gold standard, and you get support for things like unsigned integers (crazy talk I know). Java lovers, flame away...
Slashdot Mirror
I understand some of the reasons for Google picking Java, but I still didn't like it. And I'm no fan of Oracle or its ilk. What I'd like to see is a phone/tablet mobile OS plus application framework based on C/C++. One thing I've missed on Android is the difficulty of porting C/C++ *IX code (the real standard) to Java. I think this is a huge loss to android to lose ~40 years of *IX continuity and the apps show it. If you like interpreted languages, great, use or write a C++ interpreter. If you like bytecode, fine, write a C++ bytecode framework. If you like JIT compilation, find, do that for C++, wouldn't be that hard. If you like fast native compiled code, C/C++ is the gold standard, and you get support for things like unsigned integers (crazy talk I know). Java lovers, flame away...