Yeah, this is something I stressed at my place. Your Jeninksfile should set up environment variables, authentication related stuff, and call out to some build tool to build the project. The Jenkinsfile should also be configure to use a docker container to run the build within. In projects at my place that's a Docker file on the project that ultimately sets up and installs all the tools and dependencies required for a valid build environment that's just checked in along side the Jenkinsfile.

Just do an infinite loop

exec_once = zsh -c 'while true; do waybar; done'

Funny. The one time I installed it, I just stuck it on a usb, booted from it, started the installer, next, next, done.

I really didn't have much of a different experience between installing pop os Vs Ubuntu.

I guess some weird hardware thing that Pop OS doesn't provide for?

Doesn't Mint make installing Nvidia drivers pretty simple?

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).

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

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 used to be a tabs guy, somepoint over time, especially when I realized some of the edge cases I have in formatting only remain consistent when using spaces, I switched.

And over gofmt, rustfmt lets you set settings for the project. Keeps the code looking how I want, and contributers don't have to care.

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

I presume, since this whole instance is programming specifically, it makes sense to have programming communities here, even if other instances have their own.