ah, yeah, if you have an android game without built-in controller support then you’re out of luck right now, sorry.
ah, yeah, if you have an android game without built-in controller support then you’re out of luck right now, sorry.
Retroarch and Steam Link both have android apps and support controller mapping, but I don’t know of any OS-level tools.
Tra-la-la!
Starting anything from scratch is a huge risk these days. At best you’ll have something like the python 2 -> 3 rewrite overhaul (leaving scraps of legacy code all over the place), at worst you’ll have something like gnome/kde (where the community schisms rather than adopting a new standard). I would say that most of the time, there are only two ways to get a new standard to reach mass adoption.
Retrofit everything. Extend old APIs where possible. Build your new layer on top of https, or javascript, or ascii, or something else that already has widespread adoption. Make a clear upgrade path for old users, but maintain compatibility for as long as possible.
Buy 99% of the market and declare yourself king (cough cough chromium).
optional autocomplete is a nice-to-have, eager autocomplete is a pain in the ass. as long as it only completes when I ask it to, I don’t mind.
My experience with pacman was via rwfus on steam deck. I was coming in as someone with experience with apt, npm, pip, even choco and winget on windows. My expectation from pretty much every other command line tool is that commands are verbs, flags are adverbs. So having to install with “pacman -S” (or is it “pacman -Sy”?) just feels unnecessarily cryptic. Same with “nix-env -iA”. I understand that there are some clever internals going on under the hood, but you can have clever internals and sane defaults. For instance, “npm install foo” both downloads the package to node_modules and updates package.json for me, so I can see what change was made to my environment. Nix should do that.
I’ve also seen it as pacman -Sy
and pacman -Syu
and so on. I really just think “install” should be a subcommand, not a flag. That’s really my only issue I guess, I’ve only ever used pacman via rwfus on steam deck so maybe my usability problem is with that.
pacman and nix are both really neat conceptually but they both fail at the most obvious usability test, which is “I just want to install a package”; its like exiting vim all over again.
edit: yes, I know you can set an alias to pacman -Sy
or whatever, but if you need to set up an alias for a command to be usable, then I can’t in good faith recommend that OS to anyone, and I don’t want to use an OS I wouldn’t recommend to others.
If you’re gonna dismiss it like that then I’d love to hear what your pain points are. What’s so bad about containers for multi-platform applications?
basically this comes down to time and money. if you’re a hobbyist, you have lots of options available, but they take time to learn and you probably already know html. if you’re a professional, developer time is more expensive than cpu cycles and you probably already employ a web developer. unless there’s a good reason, most people won’t learn an entirely new GUI toolchain.
Electron apps ship their own chromium-based renderer, but ‘webview’ means the OS gets to use its own renderer. It’s still a browser-like environment, but at least the OS can choose the most performant one.
syncthing is the easy option if you have some files you always want to have on both. if you just want to access your desktop files from your phone, I recommend Cx File Explorer for Android, it’s a file browser that supports various network file share protocols including Samba and SFTP.