Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Here's how I did it:

Step One: Come up with some lame excuse for why you probably need a Mac. You know, Testing. Gotta make sure it looks right on Safari and all that. Maybe we'll be doing an iOS version at some point.

Step Two: Convince yourself that you'll install Windows 7 on it to see if you can maybe use it as your dev box. It'll just be a windows machine on cooler hardware.

Step Three: Go to Apple.com and configure the most pimped-out Macbook Air they'll let you specify. Hey, it's only Two Grand. That's less than your last laptop cost. And look at it! It's half an inch thick.

Step Four: Actually buy it. Get it home, take it out of the box, pick it up (between your thumb and forefinger it's so freaking light), and play with it.

(optional by this point) Step Five: Install Windows 7 and Parallels. It really does work as well as they say. It'll be the fastest windows box you've ever run. Oh, and if you're doing VS.NET web dev, specify a big partition because it won't let you run in debug mode if your project files are sitting on the main partition.

... And that's it. Now you have a Mac. It's actually a pretty cool little machine.



yeah its actually pretty slow compared to my vaio Z on Windows... and the energy saving drivers on Windows are poor at best on Macs. (by design, heh)

I am amused by the number of people who actually run Windows in // or vmware or vbox on their Mac cause they need apps that don't exist on Macs, or just have crappy support. Likewise for Linux apps which they run on OSX that way because the so great OSX underlaying unix makes it too complicated to port a couple of CLI apps (not even mentioning the GUI apps - UI toolkits for OSX all look horrible)

Running OSX is actually just to be part of the hype.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: