Before buying a Mac mini in 2005 the last time I had used an Apple product was when I started the computer lab at my high school with a couple of used Apple IIs (1983). The school let me do it because I had “experience” programming Commodore VIC20s and Commodore 64s. LOL.

I am happy to say I am back to loving computers again after buying that Mac mini ( and a MacBook in 2006 ). I tossed Firefox off my Mac after one too many crashes and recently tried Safari. I was much impressed with the speed. I decided that speed and stability are more important to me than extensibility ( in a browser ).

Don’t get me wrong, I like Firefox. I really do. But sometimes it feels slow and kludgey. It takes a long time to start up, consumes a lot of system resources, and crashes on me for no apparent reason.

Safari isn’t without it’s faults ( lack of an extension mechanism is one of them ) but it doesn’t crash nearyly as often and it’s very responsive. If my tests with the development version of WebKit is any indication of what to expect in Safari (WebKit is FRACKING FAST!), then Firefox is about to leave my desktop for a long time.

Liked this post? Follow this blog to get more. 

2 responses on “WebKit is FRACKING FAST!!”

  1. Khürt – Don’t suppose you have the ADC download of 10.5.2 + the beta of Safari. Some really cool things are right around the corner (all thanks to WebKit).

    … And, yes, HDCP DOES suck … 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Feel free to comment on this story directly above, but you can also go to copies posted to social media on the left, and reply to or comment on them there. Your responses via Twitter, Facebook, and Google+ will appear below.

To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Learn More)