• 0 Posts
  • 208 Comments
Joined 3 years ago
Cake day: July 7th, 2023
  • Lulzagna@lemmy.worldtolinuxmemes@lemmy.world•He's obsessed
    11·
    7 days ago

    This shit happened all the time, it was a non-stop nuisance, and it’s only the tip of the iceberg. Retina display would disconnect daily, peripherals would disconnect when connected through a retina display, the entire OS one time would not boot and there was no real error message but was fixed by clearing some battery cache after we already ordered a new macbook.

    These issues plagued our entire office, but you just lived with it because you didn’t have a choice. One ycombinator commentor described these issues as “papercuts”, and they’re so abundant that they moved away from MacOS entirely. Another commentor describes that the most recent release is the most “breaking” version yet. https://news.ycombinator.com/item?id=47440759

    It’s pretty ignorant to say “it’s perfect for every day use” in the face of literal users struggling to use it for “every day use”.

  • Lulzagna@lemmy.worldtolinuxmemes@lemmy.world•He's obsessed
    124·
    7 days ago

    No skill issue involved when your team arrives to work and every single employee’s screen sharing functionality stops working…and there’s no warning or notification why it’s not working.

    No skill involved when your sound drivers stop working during a presentation and you need to reboot to get them working again because there’s no way to restart the devices.

    No skill issue when the file explorer has no way to access the root directory - you have to run finder from the command bar and that somehow works.

    No skill issue involved when an update breaks all local domains and you have no way to override, so you have to change all dev domains for everyone across the whole org…TWICE.

    No skill issue when wifi and bluetooth randomly stop working and the only solution is to reboot.

    No skill issue when pressing the play button and it open iTunes when Spotify is already open.

    Not a skill issue when desktop transitions don’t accept input until the transition completes. Reducing the transition time does not help, the transition must fully complete before you can provide input.

    I could go on, but I can only recall so much anecdotal experience from the few years I suffered through that shit. Maybe some of these things have been fixed, but release after release the experience would worsen and usability would degrade. I’ll never use a mac again, my productivity is too important to me.

    Anyone who stans for MacOS are just lying to themselves.

  • Lulzagna@lemmy.worldtoProgrammer Humor•No Microslop for me
    1·
    1 month ago

    I agree, an anecdotal experience is not a substantial justification, but my experience was definitely 30+ issues in just a few year span. The entire organization just suffered through the pain - developers didn’t have an opinion or preference on workflow. There’s definitely a blind bias towards the ecosystem, even if the experiences aren’t as bad as mine.

    That being said, I’m not alone in this. Funny enough, this just popped up on HN: https://news.ycombinator.com/item?id=47440759

    The DNS issue I had back 6 or 7 years ago, a similar issue has now popped up. Each update is just a wave of frustration and issues. The comments are on tangents of other issues with the new release. The top comment says “Papercuts like this are why I moved away from macOS” and I feel seen.

    As for Docker, it’s not a cpu architecture issue, you’re almost always using x86. MacOS (and windows for that matter) don’t have the Linux Kernel features necessary to support Docker (or containers for that matter) regardless of architecture, so there’s a virtualization layer (hypervisor) to make them work. This typically will have cpu, memory, and file system overhead (expecially memory and FS). Can you develop with docker containers? Absolutely. Is it as efficient as linux? Not even close. Sometimes, I’m running between 4-10 containers which runs flawlessly on my Linux system because I don’t need to worry about a virtualization layer.

    All I’m saying is that MacOS is not the development haven a lot of people are making it out to be. I hold both MacOS and Windows in contempt when it comes to being developer geared systems.

  • Lulzagna@lemmy.worldtoProgrammer Humor•No Microslop for me
    63·
    1 month ago

    Ya, it’s wonderful having your entire organization not able to share their screen one day, and there’s no package manager, and needing several multi gig xcode binaries to install node dependencies and they change on new releases and it’s not transparent at all, and docker runs like shit because it’s virtualized, and everything is a memory hog. That’s just what I remember - I used to have a text document where I tracked every issue, I think it was almost 100 items long.

    I absolutely fucking hate Windows, but doing web development on a Mac is a fucking nightmare and takes the cake. I’ve been using Linux for over a decade now and will never look back.

    Edit: oh I just remembered the time osx broke all of our local development urls and we had to change them