Google in 2057:
"We're excited to announce that Android Tablets now have a terminal, with full support of terminal applications like 'ed' and 'grep'!"
"We're excited to announce that Android Tablets now have a terminal, with full support of terminal applications like 'ed' and 'grep'!"
I'd say past 40 years proves this model is not what people want, but they are so persistent about not doing a normal file-focused UI that it feels intentional. Like some directive from Steve before he passed.
I ended up putting Rockbox on my iPod Classic, which makes it be what it actually is: an MP3 player! (Alas the UI is not as pleasant, and battery life is worse...)
Similarly I've been so confused about files on my iPhone, whereas on Android I never had any confusion (except on some newer versions where there's both a Documents folder and a Documents "smart view" which are indistinguishable except when you realize nothing makes any sense and you ended up in the screen that's trying to give you an Apple-like files experience for some reason, and then you navigate back to the actual file system and are actually able to find your files...)
But WTH is an iPad for with the larger screen and all that power? Watching videos or maybe some games I guess?
I think the limitations are entirely for business strategy reasons, not because they believe there is no demand.
In older versions of iPadOS (it might even have just been iOS back then) you had to enable the mouse under Accessibility to make it work, but in current OS versions it "just works"..
You can even cmd-tab between apps and a lot of the keyboard shortcuts you know and love work in most apps.
Maybe in their marketing materials. Trying to do something useful on an Android tablet is painfull. The on screen keyboard uses half of your screen.
Erm... what?
> The only real way to win here is by using a VM which is what ChromeOS did.
What advantage would the VM provide, other than the host OS having even less insight into what the application is doing?
(Which is, by the way, exactly the only reason Android is introducing VMs: hiding stuff from the host Android)
The host android won't have access to the guest VMs but the hypervisor still does.
They sure as hell don’t go out of their way to help keep it running.
> Squeeze extra performance out of a device to achieve low latency or run computationally intensive applications, such as games or physics simulations.
> Reuse your own or other developers' C or C++ libraries.
Followed by https://developer.android.com/ndk/guides/stable_apis
It is not on that list, it isn't supported.
I doubt anyone at Google is trying to break Termux, but they don't care about power users and they think Android should function like their iPhone and treat users accordingly.
If it isn't on that list, it works by luck and can be broken on any device or Android update.
If that's not what you mean, I'm not sure how your link works as a reply to a comment on Google's motivation.
So naturally Google breaks "private" APIs whenever they feel like.
(And can we just pretend that I replied the same thing to the other places in the thread you posted the exact same response? No point in duplicating threads)