I already did all that. I had a Lenovo ThinkPad from 2018-2024 (RIP it died) completely Linux/Ubuntu but I really didn’t know how to use it. I just used it like windows. Didn’t know how to maximize its linux capabilities.
Thus applies to everything. Force yourself to do stuff. Install Programms that you think are cool. Dare yourself to try new software. This is what teaches you how to use Linux. Oh, this software isn’t available for your Distro and they don’t have a flatpak/snap/App Image? Compile it from source. This doesn’t work? Figure out why. Sometimes this leads to frustration and wasting a lot of time, but that’s how you learn stuff.
Great suggestion. I’m currently trying to figure out Flatpak builds because I want to try Vega Strike on the Steam Deck (the AUR doesn’t like it). As someone used to Docker and VMs, dependency management is absolutely bizarre, confusing, and hard to find documentation on.
It is amazing how much you can learn when the only way to get OpenOffice working is to troubleshoot outdated C syntax errors in the output generated while compiling with clang. Time solves even the most abstruse problems, whether you planned for it or not.
I already did all that. I had a Lenovo ThinkPad from 2018-2024 (RIP it died) completely Linux/Ubuntu but I really didn’t know how to use it. I just used it like windows. Didn’t know how to maximize its linux capabilities.
Try doing an installation of Arch, following the guide and searching how to do things as you go. It teaches a lot of things.
Thus applies to everything. Force yourself to do stuff. Install Programms that you think are cool. Dare yourself to try new software. This is what teaches you how to use Linux. Oh, this software isn’t available for your Distro and they don’t have a flatpak/snap/App Image? Compile it from source. This doesn’t work? Figure out why. Sometimes this leads to frustration and wasting a lot of time, but that’s how you learn stuff.
Great suggestion. I’m currently trying to figure out Flatpak builds because I want to try Vega Strike on the Steam Deck (the AUR doesn’t like it). As someone used to Docker and VMs, dependency management is absolutely bizarre, confusing, and hard to find documentation on.
It is amazing how much you can learn when the only way to get OpenOffice working is to troubleshoot outdated C syntax errors in the output generated while compiling with clang. Time solves even the most abstruse problems, whether you planned for it or not.
jk