As measured by XBench, Snow Leopard affects every Mac a little differently, but the basic outcome is the same: raw CPU performance goes up slightly, while the graphics numbers go down -- OpenGl performance in particular takes a big hit. We're not sure if this is due to our version of XBench not playing nicely with Snow Leopard or something else entirely, but we didn't notice any slowdowns while we actually worked -- or played a little casual CoD4. We're not deep into the benchmark scene, so we'd wait for some hardcore marks to hit before you race into fanboy battle with these numbers -- for now, just know that Snow Leopard certainly "feels" a little snappier than Leopard.
Xbench. Software that hasn't been updated since 2006, before Leopard even came out.
That they managed to break so many things with a minor upgrade of the OS - is simply astonishing.
That they managed to break so many things with a minor upgrade of the OS - is simply astonishing.
Xbench. Software that hasn't been updated since 2006, before Leopard even came out.
"We're not sure if this is due to our version of XBench not playing nicely with Snow Leopard or something else entirely, but we didn't notice any slowdowns while we actually worked -- or played a little casual CoD4. We're not deep into the benchmark scene, so we'd wait for some hardcore marks to hit before you race into fanboy battle with these numbers -- for now, just know that Snow Leopard certainly "feels" a little snappier than Leopard."
under the hood upgrade, not minor upgrade... a point update is a minor upgrade.
Apple should get their head out and do something about the most "broke with upgrade" apps - the ones using InputManager, themes like Unsanity and what not and give them a set-in-stone, frozen, predictable API.
It's not that the APIs Unsanity is using change constantly... it's that Unsanity isn't using APIs. They're messing around with undocumented internals of apps. Likewise with Input Managers; the *intent* of the Input Manager API is to allow for multilingual text input, it's only through a particular detail of how that's implemented that people use it to hack apps.
Messing the internals of apps cannot be supported in a stable way, and no system does so.
Assuming I'm interpreting what you mean here correctly, there are supported APIs for doing it on OSX as well (DYLD_FRAMEWORK_PATH and related); doesn't make 'em safe.For Windows the situation is far more tolerable - there have been supported ways of DLL hooking since long
same goes for theming APIs - uxtheme etc. Microsoft rarely broke APIs and that worked very well from them and their developers - Apple needs to start caring more about developers.
Assuming I'm interpreting what you mean here correctly, there are supported APIs for doing it on OSX as well (DYLD_FRAMEWORK_PATH and related); doesn't make 'em safe.
Do any developers other than Unsanity actually need theming APIs? Particularly *system* theming APIs rather than app theming? Catering to a particular niche could potentially be nice I suppose, but the APIs that *are* being added seem a lot more generally useful. Snow Leopard fixes quite a few developer API requests.
No loader paths are not APIs - it's just a mechanism to allow different DLLs to be loaded based on search path and order. I am talking about the hooks API. If you look at the bottom of that link - it works on all systems since Win 95 and is supported/safe.