Unfortunately, Linux manuals are pretty scattered around. I'll try to find something for you:

• If you want to learn the very basics of Linux command line, here's what I found on the web: http://www.ee.surrey.ac.uk/Teaching/Unix/ ;
• For on how to use GNU user-land tools (Bash, cat, less, grep, sed, etc.), I recommend the GNU manuals which are very well-written: https://www.gnu.org/manual/blurbs.html (example: Bash manual);
  • GNU manuals are also downloaded for offline read by default. These manuals are provided with info.
• For GUI desktop, it depends on what Desktop Environment (DE) you use:
  • KDE wiki with tutorials: https://userbase.kde.org/Tutorials
  • GNOME app overview with documentation: https://apps.gnome.org/
  • If you don't know what DE you use, KDE uses sharp edges for windows and GNOME uses round edges ( 👁️👄👁️ ).
• For system, as @Terumo@lemmy.world pointed out, for system-specific stuff, there's ArchWiki that has topics about everything.
• If you want to understand what are the /usr, /usr/local, /etc, /dev, etc. filesystem directories, you want to look at the Filesystem Hierarchy Standard: https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html
• There is also a free training course for Linux: https://training.linuxfoundation.org/training/introduction-to-linux/
• If you're a developer and want to find out how deep the rabbit hole is, you may want to look at an online book Operating Systems: Three Easy Pieces: https://pages.cs.wisc.edu/~remzi/OSTEP/

EDIT: Forgot this important material:

• If you need to know command-line argument specifics for a particular program, use manpages (For example, to find brief information about grep, type man grep in your shell, and info grep if you need a complete manual).

You can try to enroll into Linux Foundation Certified Sysadmin course. It is quite a respectable certification. Try to have some practice every day as well.

Oh really? In Lithuania, murder is also illegal. It traces back from the spoken tradition of the ancestors. Some recent analysis has found traces of this social ban in 800 years old folk tale, Spruce the Queen of Serpents, in which, as a punishment for murder, the killers were turned into trees. It is weird how Lithuanian culture shares similarities with the Japanese! There must have been cultural connections at some point in time…

I'd recommend rather boring Debian. Archlinux as well if you want to dive deeper.

EDIT: For Debian, you want Debian Testing.

I got used to XFCE, but, with my new awesome Tuxedo laptop, I got KDE as a DE for a stock OS, and I could say it feels much more complete. But the performance drops, when opening a terminal, for example.

Your web browser, Chrome, is not supported!

Please use Midori to watch The Seven Samurai.

Gun/Linux 🔫

Yes, there are.

As the others made a good point, Linux is the kernel (program that connects hardware altogether and manages processes). GNU is an organisation beginning in 1983 that made some vital userland programs (Bash, GCC, readline, GNOME, GTK, GIMP, etc.) as a replacement of the proprietary ones found in UNIX and Windows. Linux is created by a Finnish student Linus Torvalds and is not a part of the GNU project but it's been licensed under the GNU General Public License (GPL), the first free software license.

Linux is used by a lot of companies, and some of the products that have Linux inside refuse to accept the paradigm of software freedom. Examples of this are: Chrome OS, Windows Subsystem for Linux, Google Android and some (but not all) appliances (like routers) that are locked-in and contain proprietary blobs.

Therefore, in technical discussions, I use the word "Linux" to refer to the OS, as "this software is compatible with Linux". But, when I want to stress out software freedom, given a large influence of the GNU project, I say "GNU/Linux".

Context: there was a Flash game called "Bloons Tower Defense" where you put monkeys to shoot down invasive balloons with darts.

Pussy Riot

I used to use Arch Linux. It's really good, honestly, especially if you want to know how the OS components work from inside or make something custom. For anything else, I would recommend Debian and its non-snap-based derivatives (Linux Mint Debian Edition or Tuxedo OS, or KDE Neon).

IDK, I used to have a dedicated software for playing with CUDA. Most of the image-specific AI stuff from the internet require 8 GB of VRAM or more, though.

Nowadays, I don't feel the need for GPU-accelerated computing, though. If I needed, I would write Vulkan compute shaders for that thing.

There are programs (LyX, TexMacs) that implement WYSIWYG for LaTeX, TexMacs is exceptionally good. I don't know about the standards, though.

Another problem with LaTeX and most of the other document formats is that they are so bloated and depend on many other tasks that it is hardly possible to embed the tool into a larger document. That's a bit of criticism for UNIX design philosophy, as well. And LaTeX code is especially hard to make portable.

There used to be a similar situation with PDFs, it was really hard to display a PDF embedded in application. Finally, Firefox pdf.js came in and solved that issue.

The only embedded and easy-to-implement standard that describes a 'document' is HTML, for now (with Javascript for scripting). Only that it's not aware of page layout. If only there's an extension standard that could make a HTML page into a document…

Gzip is slower and outputs larger compression ratio. Zstandard, on the other hand, is terribly faster than any of the existing standards in means of compression speed, this is its killer feature. Also, it provides a bit better compression ratio than gzip ^{citation_needed}.

Yes, but only if everyone adhere to CommonMark version of Markdown.

Markdown, CommonMark, .rst formats are good for printing basic rich text for technical documentation and so on, when text styling is made by an external application and you don't care about reproducible layout.

But you also want to make custom styles (font size, text alignment, colours), page layout (paper format, margin size, etc.) and make sure your document is reproducible across multiple processing applications, that the layout doesn't break, authoring tools, maybe even some version control, etc. This is when it strikes you bad.

Open Document Standard (.odt) for all documents. In all public institutions (it's already a NATO standard for documents).

Because the Microsoft Word ones (.doc, .docx) are unusable outside the Microsoft Office ecosystem. I feel outraged every time I need to edit .docx file because it breaks the layout easily. And some older .doc files cannot even work with Microsoft Word.

Actually, IMHO, there should be some better alternative to .odt as well. Something more out of a declarative/scripted fashion like LaTeX but still WYSIWYG. LaTeX (and XeTeX, for my use cases) is too messy for me to work with, especially when a package is Byzantine. And it can be non-reproducible if I share/reuse the same document somewhere else.

Something has to be made with document files.

I once witnessed an ad on somebody else's computer "[picture of 1€ coin], only 0.99€"…

I guess I could become a millionaire if I ordered 100 million of these coins for 99 millions…

This is what journalists in New York were expecting Crocodile Dundee to be.