this post was submitted on 20 Nov 2023
497 points (86.4% liked)

linuxmemes

21222 readers
49 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 24 points 11 months ago (3 children)

    I vividly remember when a friend of mine who runs a small graphic design studio was sent an archive file macOS couldn't open natively and asked me for help. Never having used a Mac and without any clue as to which tools the stupid app shop (which was rather new at the time) held, I couldn't for the life.of me get the blasted thing to obey me, until I found a terminal. I then installed build utils and compiled the frickin' unpacker I needed myself since it only had Linux binaries. Worked like a charm.

    [–] [email protected] 15 points 11 months ago* (last edited 11 months ago) (1 children)

    I think it's gotten better, but I still have a bad taste in my mouth from the countless times MacOS was too stupid to recognize a file type, and absolutely rejected all attempts to tell it what it was. I almost always found a way around it, but it would sometimes take dozens of minutes of fighting with the OS; these times almost made me long for Windows.

    Apple's position that users are fucking idiots may be usually justified, but they consistently violate the "... and make the uncommon possible" rule. The philosophy that the OS is always right is frustrating.

    [–] [email protected] 10 points 11 months ago

    Our phones aren't bad at reception, you are holding them wrong

    [–] [email protected] 4 points 11 months ago

    I can agree that fighting apples UI's can get frustrating (i.e. playing the "try to find the right button" game). What makes me think macs are great is that you get all the freedom you could wish for in a terminal that is unix-compliant, while also getting the reliability of a hugely widespread OS that a bunch of good developers are paid to maintain. With the new macs you also get the apple silicon hardware, which is great.

    I think most people that use macs indeed do need the safety rails, but at the same time they bother me. I know how to disable them within 15 mins of setting up my computer, but if I'm helping someone with an issue, I sometimes first need to spend some time disabling safety nets and installing the tools I need. Also: Shoving iCloud storage down my throat is shit. They should stop that.

    [–] [email protected] 2 points 11 months ago

    Next time, just install hombrew 😇 in the terminal, of course