Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)YU
Posts
0
Comments
415
Joined
2 yr. ago

  • Sorting out a Mac is troublesome. Errors that give you no information, lack of easy access to advanced utilities, and of course, it bring all in the name of "It Just Works! (TM)". I found myself cursing at a Mac, but never had on literally any other operating system ever. Even TempleOS is easier to troubleshoot.

    Errors on every major OS:

     
        
    Windows: The application could not start because of missing dll X (0xb). Reinstalling the program may fix this problem.
    Linux: Could not find libfluidsynth.so.1. Reason: No such file or directory!
    macOS: Could not connect to this network.
    Android: App not installed. There's also another "There was a problem parsing the package" which either means it's corrupted or your phone is from the Stone Age.
    iOS: Literally reboots your iPhoney every 3 minutes because the fucking microphone is broken.
    
    
      

    Now let's see what those errors tell me.

     
        
    Windows: A DLL is missing. Either it got corrupted or the user fucked up.
    Linux: App is linking against a super old library. Update the app or compile it to use a newer library.
    macOS: LITERALLY NOTHING. Super vague, but at least the Android one below only appears when you are sideloading (you should know what you're doing)
    Android: While the error itself is vague, it usually means "no space left" or "bad signature". Again, if you see this error, you should know what you're doing.
    iOS: I couldn't tell unless I knew the mic was broken.
    
      

    Guess how many times my Dad had trouble with Bluetooth on macOS. More than I can count, to the point of needing to steal my mic from me.