TheDarkQuark

I used ternary for a few days (which let's you count to 59048 on two hands, 242 on one), but then realized I never needed to count that high, so reverted to binary (now, I can count to 1023 on two hands, 31 on one hand).

Just use SSH keys.

https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent

And use SSH urls (git@....) instead of HTTPS urls (https://...) when cloning.

I won't have any of them as my sibling!

Explaining like you are 5:

If you have worked with programming languages, you might have come across global variables and inbuilt functions/keywords. PATH is a similar global variable for your terminal session.

Every time you open up a terminal, you load up these "global variables", and you/programs can access them (or the applications assigned to them).

So, let's say you have your application (executable) as /home/werecat/corncob/bin/corn, instead of starting it with ./home/werecat/corncob/bin/corn ..., if you have /home/werecat/corncob/bin in your PATH variable, you can just use it as corn ....

export PATH="/home/werecat/corncob/bin:$PATH"

just means:

1. PATH = /home/werecat/corncob/bin + PATH
2. persist (export) path for the duration of this session (usually until you close the terminal tab)

If you see somewhere to add it to your /home/werecat/.bashrc file, it means "all commands in .bashrc file are auto-executed every time you start a new terminal session, so if you have it there, you won't need to manually keep entering the command over and over again".

You can list these environment variables by just running:

env

Also, recommend you have a look at https://www.freecodecamp.org/news/how-to-set-an-environment-variable-in-linux/.

Hope this helps. Good luck on your Linux journey.

I'm glad that you want to switch to Linux, but I think there'd be open source solutions for Windows too. I daily drive Linux, and I would begin with looking for open source timers if I ever need timers. Why not do the same in Windows too?

Here are a few: https://alternativeto.net/software/free-countdown-timer/?platform=windows&license=opensource

Try launching the program from a terminal, and see if there are any GPU specific log messages. May be also have a look via journalctl.

Also nvtop and nvitop gives you a GPU monitor.

The article:

https://archive.is/MObDZ

You can, but I recommend btop. It's much more cooler.

sudo: apt: command not found

For a person with not much familiarity with Linux, and just wants to check things out, I would recommend starting out with a VM. WSL is good, but that is not the "Linux experience". Moreover, if they are not already familiar with the command line, it may be a bit intimidating. The same goes for dual booting. It's more technical, and it's more appealing to just jump back into Windows when things go wrong on Linux. VM approach though, gives you a sandboxed space (with DEs and all) where you can smoothly get familiar and comfortable with Linux before making the final switch. That's my personal opinion for beginners.

That's it, I'm switching to Windows!