I am amazed, or maybe not, at the level of denial coming from many of you. One poster even went as far as to say, quote "I simply do not believe you..." in reply to Darwin when he said there is no way to make TF work with SIP enabled. Most of the misunderstanding is because of a lack of understanding how TF works. Comparing to programs like PathFinder, and saying why can't TF do that, etc is irrelevant. Those apps are separate apps, they launch and run independent of Finder. TF is not independent of Finder, it uses code injection, it LITERALLY seeks out and INSERTS its own code into Finder IN MEMORY at runtime. This is no different than what a Trojan or malware program does, Trojans and malware insert themselves into running code to change behavior. The only difference is intent, malware does it to accomplish undesirable behavior; TF does it to accomplish desired behavior. The technical process of replacing the program code is identical. And this behavior is exactly what SIP is meant to prevent, because if TF can do it, so can any other program/developer. Apple CAN NOT judge intent, it can only prevent outside programs from trying to circumvent the operating system, not the reason why.
I do not blame Apple, the reality is allowing code injection is an open invitation to malware, and frankly, it is AMAZING it has gone on this long without major infections on the Mac platform. but OS X can no longer fly under the radar and hope malware developers don't target Macs. Without SIP in place, ANY DEVELOPER could write a program that can change pretty much anything in OS X, once the user puts in their password during install. People criticizing Apple or calling SIP stupid, are IMO naive. I get it that techies and people who tweak their systems (i.e. people who use TF), feel SIP is dumb, but that is because as techies we understand how to practice safe computing. The other 99.5% non techies don't understand, and dont' need to understand, they need to be protected from themselves, and that is why SIP was implemented.
For TF to work without disabling SIP, would require a COMPLETE and FUNDAMENTAL rewrite and design of how TF works, basically TF would have to be rewritten as an app, like PathFinder or ForkLift. This would not be trivial, but a huge undertaking. It's not just changing a few lines of code here and there, it is a completely different approach and design, and Darwin understands that it isn't worth his effort to enter into a market space that is already crowded, with products that have years head start, but y'all won't listen.
Some people have said why can't Apple keep SIP, but just allow certain 'trusted' programs to make changes. The SECOND you go down that road, you have totally defeated the purpose and security of SIP. Who decides what is 'trusted'? How will you enforce? Hackers can already spoof app signatures and security signatures, so having an app signed is still no guarantee. EVERY developer in the world is going to request an exception be made for it, EVERY developer in the world is going to insist its programs are 'trusted'. Once you open a 'back door' then you open a back door to potentially anybody. Do you expect Apple to test every Mac app to see if it can be trusted, and every upgrade and update for all time? And once 'trusted' status is given to a developer, who says that developer can't start inserting 'bad' behavior into his program? What if a spyware company pays a developer enough money to use his 'trusted' status to bypass SIP and add code to do nasty things to your Mac?
As a developer myself, I understand Darwin's position. I love TF, but the writing is on the wall. Turning off SIP is a stop gap, and even though I may turn off SIP personally because I'm technically savvy and know how to protect myself, I will NOT turn off SIP or recommend it for my non technical friends and family and co workers. It's precisely those kind of users that SIP is most intended to try to protect.