> Sigh. The apple ecosystem is becoming harder to use. But I really have no choice I do a lot of iOS and MacOS development, and its the only platform I can use for that purpose.
So, first off, sincere sympathy. I feel you, I've been there.
My current recommendation to people is: whatever you do in your personal life (Apple, Android, Windows, whatever), keep your Apple-related work environment completely segregated — that usually just means one dedicated Mac and the test iOS devices. Do not use any of it for anything else than work. Do not mix a home server with work-Mac-related stuff and personal life. Do not use the same AppleID. Do not mix anything.
It's generally a good approach anyway, regardless of one's development platform/target.
It then becomes natural to e.g. never worry about NFS and simply use the "recommended" Apple path — like some Thunderbolt drive, or whatever MacOS networks with these days.
The downside that it obviously induces additional cost is debatable:
- developing for Apple systems usually translates to higher income, and Apple is somewhat "fairly" (at least in their mind) forcing some extra burden of cost on developers, but it's likely marginal for said devs (although hostile to developing markets, at first glance).
- work-related machines generally fall under different tax regimes than personal stuff, and while we surely all dabble into the grey area, it's always better to have it 100% legit work or personal but not both. Insurances etc. may care too.
So... Yeah. I hope you can segregate and rationalize the work-Mac(s) to follow Apple's best practice (whatever they push as "This is the way" for MacOS).
I've done what you suggested in this paragraph, and do this as well. It means you can't use a personal iPad with Catalina's Sidecar feature, which just sucks knowing a second monitor is almost right there.
So, first off, sincere sympathy. I feel you, I've been there.
My current recommendation to people is: whatever you do in your personal life (Apple, Android, Windows, whatever), keep your Apple-related work environment completely segregated — that usually just means one dedicated Mac and the test iOS devices. Do not use any of it for anything else than work. Do not mix a home server with work-Mac-related stuff and personal life. Do not use the same AppleID. Do not mix anything.
It's generally a good approach anyway, regardless of one's development platform/target.
It then becomes natural to e.g. never worry about NFS and simply use the "recommended" Apple path — like some Thunderbolt drive, or whatever MacOS networks with these days.
The downside that it obviously induces additional cost is debatable:
- developing for Apple systems usually translates to higher income, and Apple is somewhat "fairly" (at least in their mind) forcing some extra burden of cost on developers, but it's likely marginal for said devs (although hostile to developing markets, at first glance).
- work-related machines generally fall under different tax regimes than personal stuff, and while we surely all dabble into the grey area, it's always better to have it 100% legit work or personal but not both. Insurances etc. may care too.
So... Yeah. I hope you can segregate and rationalize the work-Mac(s) to follow Apple's best practice (whatever they push as "This is the way" for MacOS).