4 ms·
The problem is that all that skill and know-how you have about how to program a computer is invalid on Android. Your assumptions about what you should expect to
by quelsolaar 6y ago
The problem is that all that skill and know-how you have about how to program a computer is invalid on Android. Your assumptions about what you should expect to find in the android API is entirely valid. You should find Input(), Camera() or similar. But you dont. Almost everything is different, worse, more complicated and not documented.
You think you can depend on basic stuff like fopen, but it doesn't work like you expect it to. Its a minefield.
If you are trying to make some simple "hello world" application its incredibly infuriating, because what should be simple is made so hard, not least by the platform keeps insisting that "you really should learn this other language"
And for the record: You should not know who Eskil Steenberg is ahead of time, but you are welcome to get to know me now. :-)
Eskil Steenberg
- flohofwoe 6y agoIMHO the Android NDK is exactly what one might expect when Java people are trying to build a C SDK. You can physically feel their disgust pouring out of the screen ;)
- anakaine 6y agoThats both great and hilarious that you showed up to answer in person. Nice work!
- Arelius 6y agofopen doesn't work like you expect?!?
- ttflee 6y agofopen() worked. It's just no files are bundled as-is in an APK. Files must be embedded into a resource-like asset file which could not be opened by fopen(). If a library your app linked to had to call fopen() and other POSIX file APIs for these files, you were f*cked up and ended up unzipping files.
- niteshade 6y agoHi Eskil! Would love to hear your thoughts(rants?) on iOS too :)