Skip to main content

New laptop and it's a showoff: G5 vs Intel

As I left my most recent permanent job for a private gig, I had to get myself my own new laptop. Of course the machine had to be a Mac, but which one? A laptop? Desktop? I decided on laptop since it's so much more portable and I do contracting. But then - 17" or 15" and what specs, and should I shell out for a brand new model, or get the older one cheaper? To cut the long story short I went for the top of the line, most recently upgraded model of 17" MacBook Pro, with 2.4Ghz Intel Core Duo processor, 7200RPM 160Gb drive, 2Gb of RAM and a hi-resolution 1920x1200 screen. This machine on Apple store costs $3800 (with tax and apple care), but I managed to save more than a third by buying it from a dude on Craigslist. My first impression - wow! The screen is so incredible, there are so many pixels that a window dragged when onto my older SyncMaster 23" screen looks twice as large! That's because 23" screen has only 1600x1200 resolution, but the laptop packs 1920x1200 in a 17" screen. Even upgrading to 1920 pixel wide screen would still not be adequate since each pixel would be larger than on a macbook. Gotta get used to this zooming effect :) That minor inconvenience aside, I decided to run some basic tests on my older PowerMac Dual 2Hgz G5, with 1.5Gb of RAM and thought it'd be fun to share it here: Test #1: Compile ruby interpreter from scratch:
  • 17" MacBook Pro 2.4Ghz Intel Core Duo:
    real    1m3.398s
    user    0m45.229s
    sys     0m15.373s
  • PowerMac Dual 2Ghz G5:
    real    2m0.422s
    user    1m28.266s
    sys     0m29.412s
I'll add more tests as I run them, but to see an almost 2x difference between 2 year old PowerMac and a new MacBook is simply amazing. Can't wait to start using the laptop for music! Meanwhile, PowerMac is available for sale for $1000 :) Laterz!

Comments

Popular posts from this blog

Car or Auto Make-Model-Year Database : For Breakfast

Make Model What?If you like me were tasked with loading a database of recent car makes/models/years, you would start by looking on the web and seeing if someone else just has it out there, readily available, hopefully for free, but perhaps for a tiny nominal fee.?If only it was that simple... I looked and looked, and couldn't find anything that would fit the above requirements. So I thought, who would know about US car models better than Kelly Blue Book? So I went on their site, and sure enough they have a javascript file that lists all known to them makes and models of used cars. Since the file is public, I figured it's not really "evil" if I scrape and parse it for my own benefit. Disagree? Have a better source? Then leave a comment.Anyway, to cut the long story short, I'm hoping to save a day or so to someone else who may, like me, be looking for this information. The ruby module shown below retrieves and parses the javascript from KBB site into a Ruby da…

Why I Like PostgreSQL

Today I gave a short presentation at work about PostgreSQL, and why I much prefer it to MySQL.

PostgreSQL vs MySQL: Eternal Battle
I may be misreading this, but it seems that there is a recent trend within startups to move away from MySQL, probably thanks to folks like Heroku on one side (who use PostgreSQL to the extreme, and help and contribute to it's development), vs folks like Oracle on the other side, tainting the "open source pureness" of MySQL :)

At my work we currently use a mid-sized MySQL 5.1 Percona instance, which is holding up quite well I must admit. Both PostgreSQL and MySQL have definitely converged to cover most features that people want, but my leaning is still towards PostgreSQL. I just agree with it's focus on data integrity, recovery, constraints, extensibility, while some of the early decisions in MySQL's design do not agree with me at all (like truncating long strings, 1/0 instead of booleans, ambiguous group by, etc). I think that data …

On Ruby on Rails with PostgreSQL, and Acts as Paranoid

Back a few years ago I was researching differences between PostgreSQL and MySQL databases, and chose PostgreSQL because at the time it supported foreign key constraints and many other fantastic SQL extensions that make developer's life a lot easier. Today I am sure MySQL is just as functional as PostgreSQL, and it does appear to be a more popular choice as the Rails DB than MySQL. I still prefer PostgreSQL, it just feels more natural to me coming out of Oracle background, so I am probably biased (who isn't?) Anyway, in the last year and a half or so, I've been writing Rails apps that use PG-based databases and found a few random tricks I'd love to share here. Opinions differ here, but just like accountants like the ancient double entry accounting system, I personally prefer a double validation system - where Rails validates my objects before/after updates, but the database double checks this using proper constraints. Rail's validation system is very robust and ext…