Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Considering all the problems that Office 2016 has on El Capitan, it is actually entirely on Microsoft. Apple is not entitled to make every app work on future OS X updates and there were many months for Microsoft to test their apps against El Cap betas.
Apple has no obligation but they could ease the way a bit more. Also I can't blame dev's for not wanting to do multiple compatibility rewrites during any given beta process, so no, they really haven't had "months".
 
What apps? Did Console.app say that SIP blocked these apps from installing? SIP is not an issue, it's a security feature meant to prevent apps from writing to specific system locations. If your apps haven't been updated to comply with SIP rules, you should contact the vendor, Apple will not fix this.

Or they can disable SIP in about a minute if they really want to. If you know how to be carefull SIP isn't for everyone. I mean we were fine for all the years and OSX versions that didn't have SIP till now. The world didn't come to and end and no ones computer exploded because they didn't have SIP.
 
Apple has no obligation but they could ease the way a bit more. Also I can't blame dev's for not wanting to do multiple compatibility rewrites during any given beta process, so no, they really haven't had "months".

There were no major API changes for almost all apps to maintain compatibility with El Cap except for SIP, which MS shouldn't be violating in the first place. In other words, Apple did in fact ensure that developers would not have any problems for El Cap as much as they can (excluding SIP).

99% of the apps just works fine with zero change on El Capitan or even Yosemite or even Mavericks.

Microsoft chose to remain with the older APIs and write their own custom code that's fragile by nature. They were the last major vendor to leave Carbon APIs when everyone else left it for more than 10 years.

Microsoft is a big company with a large QA department that can test their apps on beta versions to make sure it works fine when it comes out.
 
  • Like
Reactions: chrfr
Or they can disable SIP in about a minute if they really want to. If you know how to be carefull SIP isn't for everyone. I mean we were fine for all the years and OSX versions that didn't have SIP till now. The world didn't come to and end and no ones computer exploded because they didn't have SIP.

Then you haven't worked in CS/QA long enough. I've helped a lot of people whose systems were unstable because they installed tools to modify their systems and it've caused them nothing but problems.

Dropbox used to cause a lot of problems with Finder because of the way they've injected into Finder until Apple killed it and offer an API for Dropbox to use, which in fact did help with stability issues. Same thing with Safari in the past before Apple offered the extensions API. SIP is going further with this.

You have the option to disable it, that's your choice but for majority of users who are not aware of how to protect themselves, they should leave SIP enabled by default.
 
  • Like
Reactions: RobFog and glhaynes
I'd be willing to try it, but that last 2 installs of 10.11.1 caused me pain; Kernel Panics. Did a clean install of 10.11, with minimal apps [Office 2016, iWork, Evernote, basic stuff]. Did a T M backup, and installed 10.11.1 B1 over it, KP's. Then cleaned and restored. 10.11 worked fine, and no issues. Then did a 10.11.1 B2, within 24 hours, KP's.

Not sure if this iteration [B3] is better, but I'll hold off for the GM of 10.11.1.
 
Could anyone check how PDFs are being rendered by Preview in the new beta, please? :)
 
Most bugs result from not doing a fresh install but installing on top of a previous OS. Apple employees have confirmed to me that this is not ideal (even though it's Apple's officially proposed method). It's been running bug free since beta 4 for me. I have around 50 apps installed and they all run smoothly. But I don't use Outlook or Exchange, so can't comment on that.

Just like with all previous updates, my system runs perfectly fine after updating. To me El Capitan is the fastest and most perfect OS X until now. It's the new Snow Leopard and even more than that.
 
Outlook 2011 is still broken, but not quite as much. It beach-balls part way through sync'ing new inbox messages. Before, it would hang earlier.

BTW, I think Apple is just as guilty as Microsoft for this issue. Apple should have made sure it didn't break in the first place.

It is not Apple's responsibility to make sure applications by other developers are compatible with their operating system. If Apple had to go around making sure every other developers software is compatible with their operating system, The operating system would never get released.

That is why they have developers build. So the developers have time to make sure their applications are compatible with the new operating system. If the developers applications get broken in the new operating system once it's released it is the developer's fault for dragging their tales and not getting it done. Same thing applies to Microsoft. It is not Microsoft responsibility to make sure Applications by other developers are compatible with their operating system.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.