Best thing is that it works flawlessly on the mobile apps as well, and Wikipedia also has a 1 million most relevant articles or so, which is just a few gigabytes.

Yeah, just a note, basically these Linux distros are the same at their “core”, but what differs among them is mostly about the software they have and the way they’re managed.

So you have distros that offer only open source software in their repository, some include proprietary drivers. Some distro families will have some differences in the path of certain folders, different families use different formats of their packages (which include the actual binary of the software together with the metadata about how to install them in the system), although a purely Linux binary should be executed in any Linux distro. Some offer more guidance during installation and setup, some offer a more “raw” experience that force you to chose every little detail, and so on.

Another difference is in their philosophy of how the packages and dependencies are made available. Distributions such Arch Linux and its derivatives always offer the latest versions of each package, reason why they’re called “rolling release”. Distributions such as Debian offer a specific version that’s “frozen” and tested thoroughly until a new version of Debian is released with more updated software.

Some say a rolling release distro is better for gamers because you always get the latest features and performance improvements, but they’re naturally less reliable than a stable distro.

So I’d say the important thing is to understand the trade-offs so that you can choose the best thing for you. And also there’s no downside of experimenting different distros in a virtual machine, for example.

Only chatGPT has these kinds of comments as if you’re seeing code for the first time. 😆

I’m not against adding comments where is needed: in the company I work for (a big bank) my team takes care of a few modules and we added comments on one class that is responsible to make some very custom UI component with lots of calculations and low level manipulations. It’s basically a team of seniors and no one was against that monster having comments to explain what it was doing in case we had to go back and change something.

For 99% of the code you just need to have good names though.

Also Windows has a button similar to “don’t update this week” or similar.

At the same time, I feel like nowadays there's less forums or places people can ask help with, although today ChatGPT can be a good help with newbie questions.

Another option is to have enough people in the company interested in using that to justify it.

In my company (a large bank) Linux is now being rolled out to selected people as test because there was enough interest from a lot of the backend crowd.

That’s what I do, except I straight up create the python venv in a folder, activate it and then do pip install yt-dlp. No messing up with my system.

This is very good.

If I was gonna make a suggestion, it would be to use some formatting tool such as black to make sure your code is styled in a standard way.

It helps to look up certain concepts in the Wiki (Arch Wiki is probably the most complete and well explained) as you come across them. The idea is to increase knowledge little by little, but over time it compounds.

Just as an example, I worked as a contractor with the biggest bank in Latin America before and basically all their server code is Java (with new code in Kotlin nowadays).

I’d go as far as saying you should know what every line of code does or you’re risking the whole thing to have unexpected side effects. When you understand what the code is doing, you know what parts you should test.