With such a slim margin of victory favoring Chrome in Windows (versus Safari on OS X), it is entirely within the realm of possibility that running these tests on a genuine Apple rig could tip the scales in favor of Safari (or back the other way). Based on what we saw in the results of WBGP2: Linux, we really didn't expect the OS X scores to get so close to the best from Windows.
PURE EDGE FOR MAC OS X WINDOWS 7
So, if you throw Safari 5.1 for OS X into the regular Windows 7 mix, Apple takes or shares second place! It appears that your Mac friends were right afterall, so stop hassling them.Īlso, remember these tests were not conducted on an actual Apple-branded Mac system. The score for Safari 5.1 on OS X is really close to Chrome 13 running on Windows 7, and it might even beat Firefox 6 for Windows.
PURE EDGE FOR MAC OS X MAC OS X
Mac OS X Lion is a beauty to behold, and its benefits aren't just skin-deep. Firefox's problems in OS X mirror what it suffers in Windows, with the addition of memory problems found in OS X. Like Chrome, though, its Windows 7 build far out-paces the OS X version. This browser suffers the same issues on OS X as in Windows 7, with the added problems of lowered JavaScript and DOM performance, as well as slower page load times.įirefox 6 is pretty close behind Opera. Opera takes third place on OS X, and its cross-platform scores are really close, earning Opera the distinction of providing a steady experience across multiple platforms. A lack of HTML5 hardware acceleration, hoggish memory usage, and poor reliability hold back Google's browser here. It also utilizes a custom version of System.Drawing that Mono originally developed for iOS users.Chrome takes second place on Lion, though its performance isn't even close to what we saw in Windows 7. In reviewing the code, de Icaza noticed that it uses native AppKit controls for some of the controls.
PURE EDGE FOR MAC OS X CODE
Navara's code comes from Mono SWF, which built a working Cocoa backend for Mono.ĭe Icaza has since decided to use this code as the foundation for a new 64-bit implementation of Mono's Windows.Forms on MacOS. Navara has made available an existing Cocoa backend that can be repurposed for inclusion on Mono proper. Navara then contacted de Iacaza to say that one of his projects may be useful in this new endeavour. This lead de Icaza to begin experimenting with Xamarin.Mac.įortuantely de Icaza was doing his development publicly, which provided an opportunity for Filip Navara to notice what de Icaza was working on.
An initial look into 64-bit Carbon suggested that the APIs by needed for Windows.Forms are poorly documented and making it hard to discern what is 64-bit capable.
His initial choices were either to use APIs provided by the 64-bit edition of Carbon or attempt a new back-end built on top of Cocoa using Xamarin.Mac. To address this gap, Mono's Miguel de Icaza recently explored how the MacOS support could be modernized. Mono's switch to 64-bit platform by default has caused problems for continuing the support of Windows.Forms on MacOS, since this support was built on Carbon's 32-bit foundation. As technology trends changed, Mono's Windows.Forms platform has not been actively developed, but does remain a common dependency for various third party libraries and applications making its support important beyond those writings WinForms applications directly. Mono has long had a pure C# implementation of the Windows.Forms stack for Linux, Mac, and Windows.
0 kommentar(er)
