Comments by "Charlie Kahn" (@charliekahn4205) on "Mental Outlaw"
channel.
-
81
-
57
-
43
-
29
-
18
-
13
-
11
-
10
-
9
-
7
-
7
-
6
-
5
-
5
-
4
-
4
-
3
-
3
-
3
-
3
-
3
-
3
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
2
-
@subspacesausage5918 The thing about Linux is that practically every separate program is nearly guaranteed to work perfectly with any other program it needs to work with. So even though you'd have to have Audacity, OBS, GIMP, Inkscape, a file manager, a 3D editor, etc open all the time, there's never a compatibility issue and files will always open with the correct program, and even editing parts of files with a different program will nearly always work. For example, if you're using Kdenlive to animate pictures in a video, and need to edit one of them, it will always open Gimp. Such is the advantage of a library-based ecosystem.
But if you want to collaborate, you either need to use a common editing protocol or all use the same central application.
2
-
2
-
2
-
2
-
2
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
@skyblazeeterno Certain tasks work way better on Linux than Windows, e.g. resource management (Windows has a lot of overhead and doesn't let you stop unnecessary processes that are part of a large environment), network drivers, GUI customization, shell scripting and commands, compilation (more compilers exist for Linux users), changing your workflow, and using alternate applications. Aside from auto-updating and tracking (which you can have on Linux anyway), Windows also has a core problem in that NTFS is objectively terrible, and a simple mass copy which would take ten seconds at maximum under ext4 takes up to several minutes. When I choose to dual-boot my machine, it's not because of any privacy concerns (your CPU logs activity anyway); it's because I almost always run into a fundamental issue with Windows that I can't stand anymore.
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
To be fair, there are a few caveats to GNU/Linux or any other Unix-like OS. For instance, most distributions do not offer a way to directly access the package manager graphically, meaning you have to know the command to use for your distribution, or go through PackageKit. As well, there are points where the entire display system crashes and you have to know some commands to get back (like, say, using your sysctl program). And many of these commands have names that people wouldn't normally guess (why use cat for printing lines, or cd for goto, or nano for a text editor?). This problem also can extend to Linux's very old and extended-upon file hierarchy. Most people would probably have no idea what goes in bin, lib, var, or etc, and I'm betting tons of people would wonder why home and usr both exist at once. Most NT users would barely even know how to use their command line, since generations of graphical tools have been built to automate things. However, since Linux is at its core a hobbyist OS which has a decent shell, people don't do that much on Linux. A decent solution would probably be for a beginner distro to list basic commands on shell startup and/or if you type in 'help', since for new users there's nothing less intuitive than a blank screen, but I have yet to see any distro do that yet.
Sure, DEs exist, and they work very well, but chances are people will need to use the terminal at some point, and right now that CLI has a UI which makes it seem difficult for new users.
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1
-
1