Captain Janeway

Well I’m guessing they actually did testing on local AI using a 4GB and 8GB RAM laptop and realized it would be an awful user experience. It’s just too slow.

I wish they rolled it in as an option though.

Why didn’t you like Hashicorps Vault? I want to know for my own edification.

I see. Well without a command line, I wouldn’t call it a terminal. I think you just want tooling to be available on an Android? It would probably look like a button or series of buttons on an app. Maybe you could connect the dots between them to insinuate a pipe? E.g., you have a “mv” button and a “file” button. When you drag from mv -> file you could maybe kick off a process that moves the file. Maybe it would prompt you for other arguments like destination? I suppose this theoretical app could allow people to install additional tooling and make their own custom commands.

But I just feel like a button UI for these kinds of things will always be awkward. If you don’t have a keyboard/terminal interface, it’s hard to implement anything that would even behave like terminals in terms of functionality.

Great examples are already in the thread, but generally speaking the answer should be “no”. Smart phones are just slow at typing. In the case of a smart phone, hitting a button is far faster than typing a command. Not to mention our devices aren’t really being used for file management, tooling, complex work, etc. So it doesn’t even make sense to have a command line unless you’re a huge unix fan or if you are doing something quite niche. And in that case, I recommend just connecting via adb.