Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
There probably won't be any 'anti-hacking' updates, but there's absolutely no guarantee that your hacks will continue to work after an update. Apple will just turn around and tell you that it's your fault for messing around and that's that :p
 
good to hear, but then again, you can't be mad at Apple when or if an update renders your hack useless, its your risk. but certainly i don't think they're going to be going out and purposefully undermining the hacks, because i think they realize its a selling point.
 
good to hear, but then again, you can't be mad at Apple when or if an update renders your hack useless, its your risk. but certainly i don't think they're going to be going out and purposefully undermining the hacks, because i think they realize its a selling point.

Right... The method for enabling syslog capture in the Darwin backend of OSX 10.4 is considerably different from OSX 10.3... When my syslog stopped working it wasn't because Apple actively sought to destroy my "hack". It was because changes to the backend structure were incidentally incompatible with the way syslog used to be enabled. It's up to me to find the right way to enable syslog to the backend so that my third party router (read: NOT APPLE'S PROBLEM) can route syslog traffic back to that machine and have it stored.
 
good to hear, but then again, you can't be mad at Apple when or if an update renders your hack useless, its your risk. but certainly i don't think they're going to be going out and purposefully undermining the hacks, because i think they realize its a selling point.

And some of those hacks may become standard features. Apple users/consumers are the best developers. ;)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.