Tempy

I mean for most Linux derivatives, getting SSH setup for outgoing connections is usually install the openssh package from your distros repos, though I imagine many preinstall it, no reboot should be necessary, and you just type ssh user@hostname into a terminal to connect to the remote ssh server to access stuff on that computer. There shouldn’t be a need to reboot for installing app that’s not a service.

Wanting to enable ssh access to the computer you are using so a remote client can connect to it? Well the same openssh package should have come with sshd which acts as the server to allow remote ssh client to connect. It’d probably need enabling (so it’s run automatically on boot) and starting (so you don’t have to reboot to have it going), on distributions using systemd that’s usually just systemctl enable sshd.service (which makes sure the sshd daemon will be started on next boot) followed by systemctl start sshd.service to start it immediately so it’s running straight away, (or systemctl enable sshd.service --now to roll both steps into one).

I’d just point out, for running an executable, wine isn’t JITting anything at least as far as I’m aware. They’ve implemented the code necessary to read .exe files and link them, and written replacements libraries for typical windows DLLs, that are implemented using typical Linux/POSIX functions. But since, in most cases, Linux and windows runs on the same target CPU instructions set most of the windows code is runnable mostly as is, with some minor shim code when jumping between Linux calling conventions to windows calling conventions and back again.

Of course, this may be different when wine isn’t running on the same target CPU as the windows executable. Then there might be JITing involved. But I’ve never tested wine in such a situation, thoughI’d expect wine to just not work in that case.

This seems incorrect, if it’s running natively, it doesn’t need to rely on wine…

Maybe. To be fair, most of what’s important to me to do what I need to do. Like individual applications are available on most other distros, and my dot files, and hence configuration for those applications, is where most of my tinkering time was spent and they are stored in repository. I share this between between my work Mac (macos) my desktop (Arch) and my personal laptop (also Arch). I would be able get going on another Distro pretty quickly if I decided to.

But I really do love Arch. I can get going with Arch on fresh machine quickly too, I now know my way around it, where to look for info, and generally just what to do to achieve what I want to do.

You don’t know me in real life. But I use Arch. It started out as a way to get a more thorough understanding of the bits and pieces that make up Linux. Now that it’s all setup and configured, it all just works, and works the way I made it work. I don’t need to tinker with it much now, unless I want to. It’s probably the only Distro I’ll use from now to the end of time, because I’m quite content with it.

Considering the many millions of steam accounts. A 1% increase is nothing to sniff at.

I started using Linux many moons ago when the LAMP stack was common for web development. (Linux, Apache, Mysql, PHP). But that was only on servers. It’s only in the last couple of years I’ve switched to seriously using Linux on the Desktop. I finally got fed up of Microsoft writing software as if using their OS meant they owned my machine and they could do what they liked with it. So I’ve switched. While windows still sits on a partition due to a couple of games, I find I’m going months without needing to touch it. I suspect I’ll be rid of windows entirely in the near future.

I mean people are going to put their hot takes wherever made them think of it. Just down vote and don’t engage. Unless especially egregious then report them

Not that they have much incentive in the first place. As history has shown, developers are quite happy NOT to make Linux ports at all. The market just isn’t big enough to care.

Once upon a time Internet Explorer was a great browser. Until they successfully forced the majority to use it.

Not on Arch it doesn’t. Almost all window managers have a package somewhere. There will be a lot of configuring, but no compiling.