Brad Arsenault (dot com)
The Blog of Brad
Posts tagged
Why I Don’t Use Firefox: Temptation
Mar 22nd
Unlike just about every other person on this earth who isn’t a n00b, I don’t use Firefox. I look at this as the result of five crucial reasons… Read the rest of this entry »
CODE: Webkit (without timer function)
Feb 24th
As noted in an earlier post I’ve been working on a script which will get the latest Webkit (nightly) build and automatically install it, delete the old file, mount/unmount the dmg, then delete the DMG…. Here is the code (I will release the timer function code soon):
on run
getwebkitURL()
set webkitURL to the result
downTHEwebKIT(webkitURL)
set desktopURL to "~/Downloads/webkit-new.dmg"
set webkitexistingfile to "/Volumes/Macintosh HD/Applications/Webkit.app"
do shell script "rm -f -r /Volumes/Macintosh HD/Applications/Webkit.app"
do shell script "hdiutil attach ~/Downloads/webkit-new.dmg"
--do shell script "ditto /Volumes/WebKit/Webkit.app /Volumes/MacintoshHD/Applications/"
tell application "Finder"
delete "MacintoshHD:Applications:Webkit.app"
move (contents of "WebKit:WebKit.app") to "MacintoshHD:Applications"
end tell
do shell script "hdiutil unmount /Volumes/Webkit"
tell application "Finder"
delete "MacintoshHD:Users:bradleyarsenault:Downloads:webkit-new.dmg"
end tell
end run
on downTHEwebKIT(webkitURL)
set webkitURL to webkitURL
set desktopURL to "~/Downloads/webkit-new.dmg"
set curlURL to ("curl -o " & desktopURL & " " & webkitURL)
do shell script curlURL
end downTHEwebKIT
on getwebkitURL()
set curlURL to "curl http://nightly.webkit.org/"
do shell script curlURL
set webkitPage to the result
set osxOffset to the offset of "<p><strong><a href=" in (webkitPage as string)
set webkitshortPage to (characters (osxOffset + 20) thru (count webkitPage) in webkitPage as string)
set dmgOffset to the offset of ".dmg" in (webkitshortPage as string)
set webkitURL to characters (1) thru (dmgOffset + 3) of webkitshortPage as string
return webkitURL
end getwebkitURL
Google Chrome-Acid3 Test
Sep 2nd
The Acid3 test (here) tests a browsers Javascript rendering ability in terms of being standards-compliant, for a reference Webkit scores 100, Opera scores 83, Firefox 3 scores 71, IE 7 scores 12, but you just get a mess (seen here), and Google Chrome (which uses the Webkit rendering engine (don’t confuse this with the browser “WebKit“, read more about webkit here) and a new javascript engine called V8-which boasts speed to kill, produces a 73 on the Acid3 test. Not bad considdering it’s the fastest to complete the test, but clearly Opera and WebKit (the browser).
@UPDATE- 9:35P
after doing some Google searching I’ve discovred that Google Chrome has scored from 61/100 to 78, this test is supposed to be repeatable, however it seems there’s some user-biased module to Chrome. My finding was that Chrome scored 73. That’s all I can say for sure.
