Having yet to test it on my Sandy Bridge i7 MBP, I can infer, in Snow Leopard, this version of Nightly will, yes, run markedly faster than on the C2D 2.0GHz — Penryn or otherwise.
Insofar as Snow Leopard on non-Xeon Macs, a Sandy Bridge dual-core or quad-core i5/i7 is going to be where we’ll see this browser shine at its brightest.
Finally got around to test-driving this on a Mac running SL.
First impressions: very good.
The first thing I do — always — when setting up a browser profile for the first time is to install a handful of prophylactic add-ons (e.g.,
uMatrix,
uBlock Origin (legacy), and
SponsorBlock for YouTube are typically my first three). I have local copies of the legacy uBlock Origin and uMatrix, and both of those installed and function as designed. SponsorBlock didn’t, even as an older version did install (but doesn’t function as designed). I chalk this up to its dependency on a relatively current Firefox codebase. Still, it would be nice to have this (should that add-on’s developer ever make a kind of “legacy” version of it).
Separately, I’m impressed it can load the YouTube front end without having YT complain about my accessing it with too old a browser and/or OS.
But most of all, I like to use
The New York Times front page to test how well a legacy browser loads the progressive elements on that page. Older browsers with earlier JS handling tend not to load and display secondary elements within that page, and more often than not, the CSS formatting in the layout of what
does parse successfully ends up being an on-screen dog’s breakfast.
So four out of five for this quick run? Not bad.
And as initial runs go, it
seems pretty stable at this test juncture. When time allows, and when I’m in Snow Leopard on my work system, I’ll give this a more thorough workout.
Thank you,
@Jazzzny , for picking up where the venerable Interweb 60.9.9 left off. Interweb was a tough act to follow for Snow Leopard browser support!