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.

If they actually wanted quality documents for people to use, they would be advocating for Standard Ebooks or something.

Or… you know… have PDFs that aren’t pictures of handwritten text?

Also… the actual good stuff has a good chance of not being free, or not being on YouTube—it’s just the reality of our world.

When you look for YouTube videos of random people, you can get anything, from good programmers to horrible ones. You can’t really require quality from strangers posting stuff for fun.

This is very good.

This kind of thing can be easily automated nowadays. It’s not really a problem.

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.

First thing I install in each platform is fish

I have friends who work at the biggest bank in Latin America, where most backend stuff used to be Java. Nowadays all new code is written in Kotlin.

I’d like to know what is it doing to be more efficient.

Another example is a large number of libraries using an external dependency to check if a number is odd.

I like how monorepo is at the bottom.

There’s a catch here, something I read someone mention on Hacker News and I agree. Python is easy when you don’t care about performance; the moment you need to worry about it, all the easiness gets thrown away.