Comment on Linux has higher share than MacOS among software developers

• some_guy@lemmy.sdf.org ⁨11⁩ ⁨months⁩ ago

  This just doesn’t track at all.

  Agreed. The bit about peripherals, in particular, seems strange. I’ve never had a problem with a fucking keyboard or mouse. None of the rest, either, but seriously, keyboard or mouse? Suggesting that they don’t work makes the whole post sound like an exaggeration.

  source

  • onlinepersona@programming.dev ⁨11⁩ ⁨months⁩ ago

    Do you use a mouse with more than 3 buttons? Do you use a split keyboard?

    source
• domi@lemmy.secnd.me ⁨11⁩ ⁨months⁩ ago

  I’m not a Mac guy so I can’t comment on the hardware side of things but I can comment on the Docker side of things.

  Docker runs in a VM on Mac, and in a VM or WSL on Windows. On Windows the experience is awful, doesn’t matter if its WSL or VM. On Mac the experience is okish but there are enough differences that it makes Docker less effective as a platform.

  The whole selling point of Docker is reproducibility, on Mac and Windows there are issues that do not occur on the platform that all the servers we deploy to run. I constantly have to help my coworkers with issues on Mac and Windows that simply do not exist on native Docker on Linux. It has gotten so bad that I simply refuse any help for anyone running Docker on Windows. I try my best on Mac but if I can’t solve it quickly or reproduce it on a Linux machine I dismiss it.

  The devil is in the detail, minor differences are enough to throw off a system that is made to be run in a container and expects identical environments between instances.

  There’s enough issues with Docker for Mac that they have separate tabs on the Docker known issues page: docs.docker.com/desktop/…/known-issues/

  There’s also 426 open issues just for the Mac port of Docker: github.com/docker/for-mac/issues

  source

  • prettybunnys@sh.itjust.works ⁨11⁩ ⁨months⁩ ago

    Huh, I mean you’re saying a lot but still.

    There are 200 open issues for docker compose, nearly 600 for docker cli.

    The number of open issues means nothing without context.

    Again, I’d love to hear about actual peculiarities you run into because as of yet in the last 5 years I’ve developed on a MBP (work provided, I previously “hated” Apple) I haven’t had these issues you’re claiming are all over.

    source

    • domi@lemmy.secnd.me ⁨11⁩ ⁨months⁩ ago

      The number of open issues means nothing without context.

      The context is that the issues for docker compose and docker CLI are almost identical across Linux hosts and can be worked around, there are 426 additional issues just for Mac one has to watch out for.

      Our main issues on Mac (that I can remember):

      • Severe slowdowns causing healthchecks to fail (Mostly caused by slow network requests and writing/reading thousands of smaller files)
      • Environment variables not being applied correctly to build containers
      • docker-compose file differences, e.g. newer versions not available or older versions deprecated earlier
      • Under high load the VM chokes even though there are plenty of resources available
      • I never was able to set permanent sysctl configs needed for some of our applications.
      • On ARM: Building some of our x86 containers is seriously slow and eats a lot of RAM
      • On ARM: Running x86 containers is much slower, sometimes hangs and sometimes even crashes the VM

      source

      • prettybunnys@sh.itjust.works ⁨11⁩ ⁨months⁩ ago

        You’ve said enough at this point for me to recognize it’s your bias speaking.

        source

        • -> View More Comments