I’ve been transitioning to Linux recently and have been forced to use github a lot when I hadn’t much before. Here is my assessment.

Every github project is named something like dbutils, Jason’s cool photo picker, or jibbly, and was forked from an abandoned project called EHT-sh (acronym meaning unknown) originally made by frederick lumberg, forked and owned by boops_snoops and actively maintained by Xxweeb-lord69xX.

There are either 3 lines of documentation and no releases page, or a 15 page long readme with weekly releases for the last 15 years and nothing in between. It is either for linux, windows, or both. If it’s for windows, they will not specify what platforms it runs on. If it’s for Linux, there’s a 50% chance there are no releases and 2 lines of commands showing how to build it (which doesn’t work on your distro), but don’t worry because your distro has it prepackaged 1 version out of date and it magically appears on flatpak only after you’ve installed it by other means. Everything is written in python2. It is illegal to release anything for Mac OS on github.

  • @thebestaquaman@lemmy.world
    link
    fedilink
    13 months ago

    Came here to say this. Just get home brew up and running. One you have gcc and your other basic tools installed, there’s very few Linux guides that won’t work on a Mac. A couple shell tools have different names, but that’s about it.

    • @farcaller@fstab.sh
      link
      fedilink
      23 months ago

      Between homebrew and nix, the amount of foss macs can run out of the box is pretty close to some generic Ubuntu (nixpkgs is technically the largest repo out there, but not all of the nixpkgs are available on mac).

      • @thebestaquaman@lemmy.world
        link
        fedilink
        13 months ago

        And that’s just regarding stuff that’s distributed pre-built with a package manager. Truth is, if you’re down to build stuff from source, you can just follow the Linux guide and everything will work right out of the box far more often than not.