• 7 Posts
  • 530 Comments
Joined 2 years ago
cake
Cake day: July 15th, 2023

help-circle
  • I would recommend installing a fairly vanilla Gnome distro (like Fedora or something) and then a KDE version (most major distros have a KDE spin) in a virtual machine. Gnome Boxes is a really easy way to do that. And then just customize the shit out of both of them and see what you like best.

    Gnome is more of a macOS-like experience so to me, it feels more trackpad driven (though keyboard shortcuts are plentiful). Install some extensions if you don’t like something. Someone else probably also didn’t like something.

    KDE is more like Windows. I’m less familiar with it but it’s on my Steam Deck so I use it a decent amount. It’s more mouse and keyboard driven, as far as I can tell. So, that’s why I think it would be fine to evaluate in a VM.

    They’re both high quality, though, so it’s really about what you prefer. I like Gnome, obviously, but I prefer to code on a smallish laptop (for portability/travel reasons) and a dock whereas a lot of people want an elaborate multi-monitor situation and a different interface. Everyone has their own workflow. Both work equally well so it’s just a matter of taste and preference. (Most Linux decisions are like that and people get weirdly angry about it but that’s part of the fun. Choose your own adventure.)




  • It’s just alphabetical so the scripts run in the right order. The numbers serve like “A” or “B” except you can add new scripts between one and ten if it comes up and your “10-whatever” file is a mess. It’s sort of a convention on Linux but not everyone does it.

    Then you just add

    for FILE in ~/.shellrc.d/*; do
        source $FILE
    done
    

    To your ~./bashrc (or your preferred shell). Replace shellrc.d with whatever you choose. I use shellrc.d on servers and stuff because the dot d is also kind of a convention for naming folders. People have their own opinions about that but don’t worry about it until you have strong opinions.


  • Personally, I put a ~/.get-going or whatever you want to call it and put all my scripts in there. Name them with numbers first like “10-first.sh” “20-second.sh” and then just put a line in .bashrc or .zshrc or whatever you like. Aliases and any critical stuff last. Then one line in your rc file can include them all.

    I made some bash scripts for distro-hopping that are now [undiscloded] years old so I can basically backup a few folders — the second being ~/bin where I put AppImages and stuff and sometimes ~/Development (I don’t always need the dev one because backups of those exist as repos) folder if I need to reinstall. A lot of people backup their whole home directory. But I prefer my method and that’s why we use Linux. I don’t want my settings for every app coming with me when I go on a new journey. Choose your own adventure.













  • Probably but they’ve designated others to do it. Like a trusted organization (Wired or The NY Times) can verify people. Some of the developers seemed hostile.

    But who gives a fuck about a blue check anyway? Even before Elon, it was a gag on Twitter when some fucking moron who interned at Reason or some shit got a big head about it and wrote as a clown to be laughed at. “Some personal news, I’m now the assistant associate dipshit at the newspaper they try to give you for free when you get on the subway.”