The option for double-clicking the menu bar does work. Just tried it.
It works for me after a reboot.. :/
The option for double-clicking the menu bar does work. Just tried it.
Here's halfway through a swipe. It uses a less pronounced shadow and just darkens and lightens the page underneath. It's annoying because the change from dark to light looks like a flicker when swiping fast. I can see the reason for it, but i'd rather for both pages to just be the same brightness.
Image capture/iphoto used to automatically open when I plugged my devices in, can't remember exactly how to disable it but I'm sure it'll be similar for Photos
I really dislike the changes they've made to the buttons on the top bar of apps like safari and pages. They've made them less flat and it looks bad. It's a regression from Yosemite. It's hard to tell exactly what they did but it looks like they made them more gray/less white and they added a slight gradient.
The whole "Rootless" shenanigan is pretty foreboding. If they make this feature difficult to disable (which requires an NVRAM boot argument even in a release specifically targeted at developers), it won't be long until we can't disable it at all and, quite frankly, it would kill OS X.
There is no skeuomorphism in El Capitan.
That color picker has been around since the Mac OS X 10.0 Public Beta or so. Nothing new, just redesigned. Honestly, half the things on that slide of features aren't really features -- which is a great thing, and we're seeing the performance benefits already.The new color picker sure is...
I think the point he was trying to make is that the whole rootless issue kind of has a negative harbinger to less user control in OS X, and a more locked down environment like iOS.I doubt it. It didn't kill the iPhone either and by far most users do not have a reason to mess with the system folder anyway. Trim Enabler is thus far the only reason I would actually care about this.
Umm, 15A179w doesn't exist...you have the latest buildWhere can I get the Developer Preview 1, Build 15A179w, I have only the 15A178w, thanks
The whole "Rootless" shenanigan is pretty foreboding. If they make this feature difficult to disable (which requires an NVRAM boot argument even in a release specifically targeted at developers), it won't be long until we can't disable it at all and, quite frankly, it would kill OS X.
I wasn't even able to disable it with that command.
sudo nvram boot-args="rootless=0";osascript -e 'tell app "loginwindow" to «event aevtrrst»'
Yes, I have done that. It still doesn't actually change the behavior of it, but it does show rootless 0 in the parameters. When I look in Disk Utility, it shows rootless is still enabled.You need to reboot afterwards.
Code:sudo nvram boot-args="kext-dev-mode=1 rootless 0";sleep 1;sudo reboot
Yes, I have done that. It still doesn't actually change the behavior of it, but it does show rootless 0 in the parameters. When I look in Disk Utility, it shows rootless is still enabled.
Then why doesn't it let me edit/remove/do anything with system files?The command will not change what Disk Utility shows but it does disable the Rootless protection.
I think the point he was trying to make is that the whole rootless issue kind of has a negative harbinger to less user control in OS X, and a more locked down environment like iOS.
Then why doesn't it let me edit/remove/do anything with system files?
I don't consider my Mac a computer anymore if I can't do something at the root level, which is the highest level of permission you can have on a UNIX system.I know what they meant and I stand by my point. I don't think the result will be all that dramatic. The writing has been on the wall for some time now and Apple has never been truly supportive of third-party system-level modifications. Most users will probably appreciate the continued level of security that they have enjoyed for years, as well as the elimination of one more problem area (changed permissions of system files and folders). Overall, it just doesn't really concern me, even though I'm one of those users that has no access to native Trim support because of it.