3 ms·

I don't even Google most of my commands anymore, unless I'm pretty sure I'm running into some weird distro-specific issue. These command easily gets me through

I don't even Google most of my commands anymore, unless I'm pretty sure I'm running into some weird distro-specific issue. These command easily gets me through most of my day now: man [thing I want to know about] [command I'm trying to run] --help There is a learning curve for Linux, but realistically, I found it to be about the same learning curve as using anything I hadn't used before on a Windows system. For basic tasks, Ubuntu Desktop is pretty darn fantastic at working out of the box, and its Software Manager parallels the Windows app store quite nicely for programs that do normal things. (Web browsers, ftp clients, office software, music players, etc etc.) I choose to run something more complex (Arch linux, presently) because I want to know more about my system, and because I like experimenting with desktop environments. But once you understand how one package manager works, you can perform most basic system administration tasks between the various distributions without a huge amount of effort, and the package manager takes care of most of the fiddly configuration details for you in the process. I find this far easier than trying to set up services in Windows, or dealing with the awful registry. Of course, I do still keep Windows around. I have a dual boot on my home desktop, and I boot into Windows regularly for the sole purpose of playing games. For all the things I love about Linux, the one thing the community still hasn't gotten down as well as a Windows system is proper GPU acceleration. For now, Windows takes the cake easily on that, and it's reasonably stable when that's all I use it for.

brokenmachine 10y ago
Yes, man [command] is good 95% of the time. Weirdly it doesn't seem to always show the options I need though, it sometimes just shows the basics, and I need to google "manpage [command]" to find the one I want. I do find the lack of standardization on command arguments slightly annoying in linux... Is it [command] --help, [command] -h, or just [command] by itself? It would be nice if there was something that could be relied upon. Also handling of filenames with spaces could be standardized as well. Is it -0, -print0, or --null to get null-termination? I always forget which program wants what. Unfortunately, I have to keep Windows around for Ableton Live. Linux is not great for professional-ish audio.

brokenmachine 10y ago

Yes, man [command] is good 95% of the time. Weirdly it doesn't seem to always show the options I need though, it sometimes just shows the basics, and I need to google "manpage [command]" to find the one I want. I do find the lack of standardization on command arguments slightly annoying in linux... Is it [command] --help, [command] -h, or just [command] by itself? It would be nice if there was something that could be relied upon. Also handling of filenames with spaces could be standardized as well. Is it -0, -print0, or --null to get null-termination? I always forget which program wants what. Unfortunately, I have to keep Windows around for Ableton Live. Linux is not great for professional-ish audio.