This might be old news to many out there, but I just got my New Black MacBook, subsequently throwing myself on the joy of Setting Up Your New Awesomely Cool Machine. After going through the basics (stripped-down OSX, Developer Tools, and a few of my favorite apps), I decided I’d maybe have to stoop down to actually consider running Windows on my New Black Macbook.
Now why the hell would I want to do that? Easy. I’m running a small web app development business, meaning I need to do a lot more things than a straightforward hardcore programmer would.
I need to assist never-getting-it-straight clients with their applications , troubleshoot, configure and generally deal with all the things a sane developer wouldn’t want to touch with a 12-foot stick. And I can’t start sentences with “Press the Apple icon top left”, because 0% of my web application clients up to date are Mac users.
I also need to test my web apps on as many system configurations I can, and this means I at the very least need a WindowsXP Machine filled to the brim with browsers and email clients and whatnots.
Up till now I had this Win Machine that everyone seems to have at his place, but doesnt really remember when he bought it exactly, or indeed, if he bought it. You know the one: It used to be gray, but now it is aged-iced-coffee-scars all over that yellow-gray depressive-looking color you can only get by getting you and your friends to smoke a lot in a confined space with a lot of hadware stashed around you.
I hated sitting in front of that thing.
I had tried the pre-MS Virtual PC on my trusted G4 Dual 867Mhz. Didn’t work for me. I couldn’t get a definite user experience by sludging through app pages like I was running a 486 box. Hence the aforementioned Machine From The Gray-yellow Lagoon.
So back to the MacBook. Now that I had the ability to run windows natively, I naturally tried it out. After the initial shock of finding myself looking at that ghastly black Windows loader screen on my New Black Macbook’s screen, and a failed attempt at installing the Apple drivers CD bootcamp burns, all was as expected. Good. Good. Of course, now that I was here, I’d probably have to install a copy of Photoshop (being a designer) and maybe a couple of editors, probably a FTP client… You catch the drift. Can’t log in and out of Windows just to change that .PNG file to .GIF because once more you forgot that IE STILL doesnt correctly render opaqued and transparent PNG’s.
Cue Parallels. Big downside, not free. But, pretty cheap. So I gave it a go. I still had VirPC freezing flashbacks back then, but tried it anyways. Not bad. Not bad at all. Pretty fast actually… by now I had also discovered that Firefox plugin that Embeds IE tab right into FF, which actually expains far better than I can why Parallels is a better development tool that Boot Camp. You can’t beat the flexibility of having two engines both running at the same time, and doing so smoothly enough to leave you work between them undistracted.

Yes, the 8 MB VideoRAM parallels forces on the virtual Win system messes with the interface a bit while performing memory demanding operations, but hey, now you got windows running side by side with OS X, you dont really need anything in there other than your IE Tabbed FF!
8MB VideoRAM will suffice. Unless what you REALLY wanted was finally getting to play FEAR.
Digg BootCamp bashing