21–30 of 256 posts
Since most of my tools are cross platform, (jetbrains ides), my work can just continue Grimm one place to another using GitHub for synchronisation.
> There are still many things I need to set up on the new laptop, for example: suspension/hibernation on closing the lid doesn’t always work Sounds like a problem of hardware not designed for Linux. Everything has been working out of the box for me on a Librem laptop.
Ditto on most non Nvidia equipped ThinkPads. Typically Dell also does a good job at Linux compatibility but sometimes things take time to be worked out on newer hardware.
1. Wait about 6 months before purchasing newly released hardware (new generation of GPU, network adapter...) to let drivers trickle down from the manufacturer to the kernel and then to the distribution.
2. If it has an Nvidia logo on it, leave it on the shelf.
Getting your custom stack tuned feels great, but maintaining that entire stack across updates is daunting. You can't join meetings because your headphone/ mic/ video drivers aren't working? yikes. i trust apple to handle hardware and os for me. I've switched to: macOS > brew (basic cli utils & gui apps) > some basic zshrc (not ohmyzsh) > docker (not environment managers) > done. ^ but i've lost trust for them to hand…
> You can't join meetings because your headphone/ mic drivers aren't working? yikes. I really don't know where you're getting this from. This isn't 2004 and you don't have to screw with ALSA drivers to get basic audio functionality on Linux. On both PulseAudio and Pipewire, I've never had this problem and I know many others who haven't had issues either, and I really just don't think audio input/output is a gigantic…
Getting your custom stack tuned feels great, but maintaining that entire stack across updates is daunting. You can't join meetings because your headphone/ mic/ video drivers aren't working? yikes. i trust apple to handle hardware and os for me. I've switched to: macOS > brew (basic cli utils & gui apps) > some basic zshrc (not ohmyzsh) > docker (not environment managers) > done. ^ but i've lost trust for them to hand…
i agree. the mental overhead is too much for me to justify, personally, for my own machine
Can an Arch person explain to me why their approach is worth it over something with a more comprehensive package manager like apt or dnf? I don’t mind compiling programs myself when needed, but for most things I’m happy to not have to hand-hold my OS when it comes to updates. From the wiki: > Before upgrading, users are expected to visit the Arch Linux home page to check the latest news, or alternatively subscribe to…
The main thing that people like about it is the rolling release model; new packages for virtually everything are updated within hours or days of an upstream release, with incredible practical stability.
> > Before upgrading, users are expected to visit the Arch Linux home page to check the latest news, or alternatively subscribe to the RSS feed or the arch-announce mailing list > Like... why?
That's very much a "cover-your-ass" type disclaimer, like a ToS that says you have no right to expect anything to work. In practice, 99.99% of upgrades work completely unattended, and in the .01%, you see a failure, you go to the News site and it says "sorry, we made a backwards-incompatible push, please delete this path before upgrading" or something like that, you do it, and then everything is fine again for another 18 months.
Arch still has the vestiges of this reputation as a wild-west distribution for reckless code cowboys, but in practice it is the de-facto "set it and forget it" distro. I spend literally 10x less time worrying about my distribution and package manager when I'm on Arch then on any other computing system I've ever encountered.
Can an Arch person explain to me why their approach is worth it over something with a more comprehensive package manager like apt or dnf? I don’t mind compiling programs myself when needed, but for most things I’m happy to not have to hand-hold my OS when it comes to updates. From the wiki: > Before upgrading, users are expected to visit the Arch Linux home page to check the latest news, or alternatively subscribe to…
Earlier quoted context omitted.
Sometimes there are some manual interventions that you may have to perform.
Yeah, exactly. Why?
There's no fixed release schedule that promises total compatibility at the cost of running years old releases.