• MerchantsOfMisery
    link
    fedilink
    arrow-up
    2
    arrow-down
    2
    ·
    3 years ago

    BetterSnapTool, OpenMTP, and AutoRaise solves 3 of the main issues the author was having. All fantastic programs that have worked well for years on Mac OS.

    Personally, I can’t stand Linux/Ubuntu because of how incompatible it is with most workplace’s software. I’d like to make the switch someday but Linux desktop distros still aren’t even close to being ready yet, IMO.

    • electrodynamica@mander.xyz
      link
      fedilink
      arrow-up
      13
      arrow-down
      1
      ·
      3 years ago

      The whole “workplace” argument was always dubious to me. If you ever actually have had to deal with those workplace environments on a daily basis the workers are constantly struggling with issues of how shitty their standard proprietary software is. Their productivity could always be improved by switching to FOSS.

      • MerchantsOfMisery
        link
        fedilink
        arrow-up
        5
        ·
        3 years ago

        I completely agree that the workers do struggle with garbage proprietary software.

        The problem is that unless a large scale shift is made, switching to Linux will just cause even more of a workflow disruption because you won’t be able to use the same, albeit garbage tier proprietary software that everyone else has to use.

        I’m pro FOSS and I’d love it if my field shifted away from proprietary software but until it does, me switching to Linux only puts me at a massive disadvantage.

        • bringleborper@lemmy.ca
          link
          fedilink
          arrow-up
          3
          ·
          3 years ago

          “I’m not going to use Linux in the workplace because there are isn’t the software I need for it”

          “We’re not going to port our software to Linux because no one uses it in the enterprise”

          The cycle continues…

          • MerchantsOfMisery
            link
            fedilink
            arrow-up
            5
            ·
            3 years ago

            It’s not really a cycle like that, I don’t think. It’s usually just because nobody in charge of software (i.e a department’s IT team) wants to deal with the inevitable wave of complaints and "things USED to be good until you started this new BS!" comments.

            Sure people may get used to the change in the long run, but often times that involves the person who was originally responsible for the change to get fired and then the next guy replaces him to manage the chaos while saying “blame the last guy!”.

            Also, money plays a big factor in this. Microsoft along with a lot of proprietary software companies know how to grease the wheels by exploiting corrupt administrators and higher ups.