sekhat

Minikube is excellent for that already.

Linux is a full time and never ending experience, the rabbit hole you want/will dig deeper in hope to find a white rabbit !

While Linux can certainly be such an experience, it doesn't have to be at all.

If you have a defined use case for your system, and there's Linix software to support that, it often just install something like Linux Mint, install the software you need from the repos, and wahoo, you have a computer to do what you need and you just use it.

Which, for most people, is how they use their computer anyway, a few bits of software they just use to do what they need to do, no need to tinker, problems unlikely to arise.

But these people are the type that don't care, they'll use what comes with the computer they bought, and just be happy, and thus will likely never try Linux.

For those of us who like to stay in the know and on the bleeding edge, and tinkering and understanding, then it's a full time thing. But we're such a small minority.

With vscode's "Remote Containers" plugin at least, it's clever enough to install that into the container after building the image. So the image built from the dockerfile doesn't contain the vscode stuff.

I'd be more interested in knowing how many people are sticking with Linux.

What issues besides insert windows program doesn't work.

Places where the average switcher has problems that aren't just user error or misunderstanding some fundamental difference, but good places that the community can investigate and improve on.

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 mean having control over everything also means you have control to not exercise control. Android as a phone OS, depending on what the phone manufacturer has changed, has pretty sane defaults. I can't say I've ever seen the need to switch to iPhones. My Android phone works excellently as a phone.

While Nvidia isn't as great on Linux as other cards. It generally works. It's pretty much fine on Xorg, slowly getting there with Wayland. At least using Nvidia with Hyprland which wlroots based Wayland compositor worked for most cases.