It’s basically what the Steam Deck does, and for a gaming device it makes a lot of sense. The vast majority of games will probably be installed to the user’s home folder anyhow…
It might be that some games require additional libraries that don’t come with the immutable base OS, but you can always install them in a custom folder (like, the game’s install dir), or just install Steam and use the Steam Runtime for everything.
And, as you said, a lot of open source tools and games (DosBox for instance) are available as Flatpaks too.
After finishing my second playthrough of Loren the Amazon Princess, I’ve now started Tales of Aravorn: An Elven Marriage. And I must say, it is pretty good. From what I can tell up to now, I like Elven Marriage more than Loren, so it’s a bit sad, that it didn’t sell that well…
Apart from that I’m playing way too much Against the Storm. It’s a pretty fun city builder rogue-like. Basically Settlers, but only the fun parts, with a bit of random challenges sprinkled in.
I also tried to play Albion (the DOS game) again, but I died in my second battle and hadn’t saved from the beginning… 90s games were something different, when it comes to difficulty. I will definitely start over again soon, this time actually saving frequently.
On the topic of Visual Novels: I’d like to recommend basically everything from Winter Wolves Games that is tagged as RPG. The classic is of course Loren the Amazon Princess, but, to be honest, their writing has improved since then, so you might want to check out their newer Tales of Aravorn games, like Seasons of the Wolf. Also, Loren is really long, so if you don’t have a ton of time, the newer, shorter games might be a better choice.
A word of warning though, by Winter Wolves themselves: mastodon.social/
Apart from Subnautica, which only is tedious regarding food/drink in the very beginning, I enjoyed Unreal World a lot. It is turn based, so there isn’t any real-time time constraint imposed by in-game hunger/thirst. It also tries to feel realistic in a lot of aspects, including the amount of food/water your character needs. While at game start you of course need to focus on immediate survival (though, that depends a bit on the scenario you play), that focus shifts rather quickly to preparing for the winter, as in stocking up supplies (think: smoking/curing meat/fish, gathering fire wood,…), and building a shelter that you can heat, so you don’t freeze when it gets cold outside. Since the game is set in fantasy iron age Finland, you probably also want to build a sauna 😉.
Even before Proton Valve was heavily invested in Linux gaming.
SteamOS has been around way longer than Proton, and the Steam Client had a native Linux version for such a long time, I don’t even remember when it was published. Also, the Steam Linux Runtime is something worth mentioning - it is a common base that game developers can target instead of the various different distributions.
There are plenty on the web (for instance on handheld.quest), but I haven’t found a single one that contains all details…
So, I’ll just try to sum up the details here:
First things first: SSH stands for Secure Shell, and is basically an encrypted remote command line, but it offers much more features than just a command line, including, but not limited to, file transfer. The file transfer feature is also known as sftp, and generally considered to be the successor of the more well known ftp protocol.
The very first thing I would do on the Steam Deck would be to set a host name in the settings, such that you don’t need to use the IP address to address it over the network. Screenshot (I totally haven’t just found by googling).
The Steam Deck comes with an SSH server pre-installed, you need to enable it though. The following steps need to be done on a terminal, in desktop mode. The terminal that’s installed on the Steam Deck is called “Konsole” (if I remember correctly). Once you have a terminal running on Desktop Mode, you can enable the SSH server via the following steps (I’ll link the help for all commands I mention, so that you can verify that I’m not trying to trick you into doing something bad):
First you need to get administrator (“root”) access to the Steam Deck, what can be done by setting a password for the default user. Don’t worry, the Steam Deck won’t start asking for a password on startup, it’s just required in order to get admin access. The command to set/change the current user’s password is simply https://manpage.me/?q=passwd. While typing the password, there won’t be any feedback on the screen. This is normal.
Once the password has been set, you can use the https://www.man7.org/linux/man-pages/man8/sudo.8.html command to run other commands as administrator. sudo will ask you to confirm your identity by entering the password.
To stop the SSH server again, you can use sudo systemctl stop sshd.
To enable autostart for the SSH server, sudo systemctl enable sshd (but I would not recommend this unless you disable password based logins - see below)
To disable autostart for the SSH server, sudo systemctl disable sshd
On the PC from which you want to connect to the Deck you will need some kind of sftp client. On Linux most file managers have sftp functionality built-in. On Windows and MacOS one needs a special program for this though (afaik). There are many, many alternatives here (just search “sftp client” in your search engine of choice), but the most well known one is FileZilla, which works on Windows, macOS, Linux and many other operating systems. I recommend FileZilla for two reasons. The first is that it’s open source (and free of charge), the second one is that I personally like it as a tool. At work I (have to) use Windows, and whenever I have to transfer files to a remote system like our webservers, our contractor’s cloud storage, or simply to copy a few music files from my phone to the office PC (yes, I am this old), FileZilla is the go-to solution for me.
If you have started the SSH server on the deck, you should now be able to access its contents via sftp. The default user on the Steam Deck is called deck, the password is the one you set earlier using the passwd command. If you are lost using FileZilla, there’s a user’s guide online.
Now, as promised, a few words on security and autostarting the SSH server. If you plan on auto-starting the SSH server on the Steam Deck, I would recommend to set up a means to connect to it without a password, and then to disable password-based SSH connections. The reason is that the Steam Deck, as a mobile device, will quite likely end up in insecure or otherwise untrusted wireless networks, and passwords are really not the most secure way of user authentication… Since SSH is a full remote access protocol, anyone who guesses your password and can reach the deck over the network could do anything on it. Given that the deck’s battery runtime is already short enough even if there is no bitcoin miner running in the background, you probably don’t want password based logins via SSH enabled permanently.
That’s where Public-key authentication comes in. You can configure the SSH server to allow users to connect without a password, if the users have access to a private key for which the corresponding public key is known to the server. To enable this, all you need to do is to create a public/private SSH key pair, and upload the public key to the SSH server on the Steam Deck. The exact process of creating those keys is again depending on the operating system. Here’s a guide about SSH key generation that includes instructions for macOS and Windows. On macOS or Linux the instructions are actually identical. You just need to open a terminal, and, if they don’t exist for your user yet, run https://manpage.me/?q=ssh%2Dkeygen to create the keys. Then you can use https://manpage.me/?q=ssh%2Dcopy%2Did to upload the public key to the Steam Deck. Once that is done, if your system uses https://manpage.me/?q=ssh%2Dagent, connecting via public key should “just work” - also in FileZilla. If you don’t use ssh-agent, you can try these steps in FileZilla.
Once you have confirmed that passwordless public-key logins are working, you can edit the file /etc/ssh/sshd.conf on the steam deck. You’ll need admin access, so the easiest way to do that is probably to run sudo nano /etc/ssh/sshd.conf on a terminal (nano help). The relevant change is to replace the line #PasswordAuthentication yes by PasswordAuthentication no (here’s the help file for sshd.conf). In order to apply these changes, you probably need to restart the SSH server: sudo systemctl restart sshd.
Enable SSH access (but make sure it only accepts key-based logins - password based on a mobile device that might operate in untrusted networks is a bad idea).
If you enable SSH, you can transfer files from the PC over WLAN. (If you are on Windows: FileZilla is your friend.) Also, you can remote access the Steam Deck command line via SSH. (If you are on Windows: PuTTY is your friend.) That’s way less annoying than having to type longer texts (think: script files to launch emulators) with the on-screen keyboard.
I’m not an artist - my 3D modelling experience can be summed up as “none”, so I can’t really answer your last point. I know for certain that we don’t use normal maps to the extent they could be used, and therefore have way more detail in the meshes than they would need to have. I’m also pretty certain that we don’t do any tesselation on player pawns, and I think (but am not certain) that this is due to some engine limitation (again, don’t quote me on that, but iirc Unreal doesn’t support tesselation on skeletal meshes on all our target platforms).