> Let's say you want to do something simple like... find out if your team members are busy before sending a meeting.
That's a standard task for business calendering, not personal calendering. It also has little to do with the front-end software and much more to do with back-end support. Calender.app supports Free/Busy and business scheduling if you're on a server that supports it like Exchange.
> Or let's say I want to manage multiple calendars, one with read, one with write access...
You can use Calender.app just fine?
You should at least have up-to-date information if you're going to shit on others choices. It hasn't been "iCal" in 2-3 years, which is a good indicator that your information is very out of date.
> Seriously that's their solution here. "Oh I see you're running 3rd party software, you need to uninstall this."
Dell will tell you the same thing. OEMs support their initial configuration. If it KPs in that configuration, they will support it. Likewise, if your Dell bluescreens with the OEM image, they will support that too.
If it's caused by a 3rd party kernel extension in OS X or a bad driver in Windows, they won't support that. No OEM would.
That's a standard task for business calendering, not personal calendering. It also has little to do with the front-end software and much more to do with back-end support. Calender.app supports Free/Busy and business scheduling if you're on a server that supports it like Exchange.
> Or let's say I want to manage multiple calendars, one with read, one with write access...
You can use Calender.app just fine?
You should at least have up-to-date information if you're going to shit on others choices. It hasn't been "iCal" in 2-3 years, which is a good indicator that your information is very out of date.
> Seriously that's their solution here. "Oh I see you're running 3rd party software, you need to uninstall this."
Dell will tell you the same thing. OEMs support their initial configuration. If it KPs in that configuration, they will support it. Likewise, if your Dell bluescreens with the OEM image, they will support that too.
If it's caused by a 3rd party kernel extension in OS X or a bad driver in Windows, they won't support that. No OEM would.