3 ms·

My entire C/C++ development cycle. I haven't touched it in years because of this. If what you want to do is bang out a GUI in Xcode you'll have a pretty good ti

by R0b0t1 6y ago

My entire C/C++ development cycle. I haven't touched it in years because of this. If what you want to do is bang out a GUI in Xcode you'll have a pretty good time, if instead you want to interact with your hardware or other software in ways Apple didn't predict then you're probably just not going to be able to do it. I can accept that this works for most people. They don't want to mess with the UI and want to "solve problems." But for me the two were linked, and I had to ditch OSX. I had similar problems on Windows but Windows lets you work around the OS if you really need to.

Wowfunhappy 6y ago
Have you looked into Macports (or Homebrew) at all? At the command-line level macOS is really quite like other Unix systems, once you install a bit of standard tooling. The semi-exception where I occasionally run into problems is TCC. It's usually not a bother on the command line, but starting with Mojave it can occasionally interfere. But, since Mojave came out in late 2018, if you haven't touched macOS in years you didn't run into that. :) (I really really really hate modern TCC...)
- R0b0t1 6y ago
  Yes, I used homebrew extensively. It helps but does not solve every problem. There's still things Apple does not want you to do and you will not do them.
  - Wowfunhappy 6y ago
    Okay, I'm still quite curious what specific development tasks you're able to do in Linux but feel restricted from doing on macOS. If you turn off SIP (takes five minutes), you can rewrite kernel memory if you want to. Which is of course a different thing than ease-of-use, but I'm not sure what would be so different.
    - jki275 6y ago
      I'll echo this, I develop C/C++ on OS X every day. Have no issues with it at all.