3 ms·

This is likely a huge part of it. I'm primarily macOS but have a LOT of experience with Windows. I still feel like I'm fighting against Windows to do anything

This is likely a huge part of it. I'm primarily macOS but have a LOT of experience with Windows. I still feel like I'm fighting against Windows to do anything. I just think different people are suited to different workflows & macOS and Windows are very very different to each other.

SparkyMcUnicorn 6y ago
I'm in the same boat as you. I was primarily Windows for many years, but reluctantly made the switch to MacOS for my daily driver a few years ago and I'm glad I did. Still have a Windows 10 machine, and although I do have some love for a few Windows-only applications, it just feels like an uphill battle whenever something isn't working.
ricohboy 6y ago
Tell me about it - I work a support desk for an MSP; all Windows. I can't tell you how many times I've struggled with file permissions or partitions that I know would be very easy to fix in a *sh shell... Imagine being told "access denied" when you're running the command prompt as "administrator"!
- Wowfunhappy 6y ago
  > Imagine being told "access denied" when you're running the command prompt as "administrator". Coincidentally, I run into this on macOS due to System Integrity Protection. But what I like about SIP is it's easy to turn off and never be bothered by it again...
R0b0t1 6y ago
Having done dev on OSX you are going to be constantly fighting the machine. Apple is worse about walled gardens than MS is. With Apple, you need to do exactly what they want or you will have pain.
- Wowfunhappy 6y ago
  Where exactly do you feel like you’re fighting with macOS?
  - 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.
FuckButtons 6y ago
I find the opposite, every time I find myself using Mac OS I find myself fighting to try and do things that should be easy but are instead convoluted.
- dlivingston 6y ago
  Can you give some examples? There are exactly two things that I wish macOS would copy from Windows: full paths visible and interactive in Finder, and the ability to create new files within Finder (how is that not a thing?!)
  - arm 6y ago
    Finder has been able to show interactive, full paths since Mac OS X v10.5 Leopard; it’s just not enabled by default. To enable it, make Finder the active application, then click View → Show Path Bar (or use the keyboard shortcut ⌥⌘P).

SparkyMcUnicorn 6y ago

I'm in the same boat as you. I was primarily Windows for many years, but reluctantly made the switch to MacOS for my daily driver a few years ago and I'm glad I did. Still have a Windows 10 machine, and although I do have some love for a few Windows-only applications, it just feels like an uphill battle whenever something isn't working.

ricohboy 6y ago

Tell me about it - I work a support desk for an MSP; all Windows. I can't tell you how many times I've struggled with file permissions or partitions that I know would be very easy to fix in a *sh shell... Imagine being told "access denied" when you're running the command prompt as "administrator"!

Wowfunhappy 6y ago
> Imagine being told "access denied" when you're running the command prompt as "administrator". Coincidentally, I run into this on macOS due to System Integrity Protection. But what I like about SIP is it's easy to turn off and never be bothered by it again...

R0b0t1 6y ago

Having done dev on OSX you are going to be constantly fighting the machine. Apple is worse about walled gardens than MS is. With Apple, you need to do exactly what they want or you will have pain.

Wowfunhappy 6y ago
Where exactly do you feel like you’re fighting with macOS?
- 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.

FuckButtons 6y ago

I find the opposite, every time I find myself using Mac OS I find myself fighting to try and do things that should be easy but are instead convoluted.

dlivingston 6y ago
Can you give some examples? There are exactly two things that I wish macOS would copy from Windows: full paths visible and interactive in Finder, and the ability to create new files within Finder (how is that not a thing?!)
- arm 6y ago
  Finder has been able to show interactive, full paths since Mac OS X v10.5 Leopard; it’s just not enabled by default. To enable it, make Finder the active application, then click View → Show Path Bar (or use the keyboard shortcut ⌥⌘P).