Quote:
Originally Posted by Hellmark
Binary compatible, kinda, sorta, not really. Compile something for ubuntu on your PC, and it will not run on your android phone. Different CPU architectures squash the binary compatibility right off the bat.
|
Indeed, which is why I made sure to say "compiled on my Reader."
Quote:
|
Say that isn't a problem, you still have the dependency issues. Your average app for Linux requires a X server, libc6, then probably the GTK or QT libraries. Android doesn't have any of that. If you're talking about a command line app that is written with no dependencies (which is pretty much just simple stuff like "Hello World"), well, how would you view that since typically you aren't allowed to see a terminal? That squashes the idea of an interactive command line app. Plus Android has some security protocols in place to limit what can be done on a nonrooted device, which would include running apps outside of the Android java framework.
|
Good points all. Again, why I said shared libraries in existence, though I should have specified versioning as well, but then we would get in to minutiae... oh wait!
An interesting point you bring up further about Android... which I have no experience with as of yet...
Android is considered the most
closed operating system on mobile devices! I think Ars Technica ran the article. That's what you're referring to with "security protocols" and the need to "root" the device. As an iPhone user, I was horribly disappointed by this revelation, since I would love a device that i don't have to root (jailbreak), and up to that point just assumed Android was wide open. And security protocols... eek, no idea what those entail, except probably a big headache!
Not intending to trash Android at all -- well maybe a little
-- since I think it's overall a good move by Sony (except for the possible loss of LRF, which is a horrible move!).
-Pie