So in my previous post I've outlined some of the better features that go along with converting over to OS X; specifically on a MacBook Pro. As opposed to making one giant post I've decided to split it up into 3 posts, the good, the bad, and the ugly. Whether or not I will actually make it to the ugly part, or decide how to separate the "ugly" from the "bad", still has yet to be determined. Some of these are really nit-picky things and others are somewhat legit problems, take them as you will... but here goes!
The Keyboard (and TouchPad)
As I'm sure everyone knows, any Mac keyboard/mouse hardware is somewhat unique. The main features of the the keyboard and touchpad combo on the MacBook Pro are as follows:
- Inclusion of a "command" (aka Apple) button
- Inclusion of specific function buttons (volume, screen, keyboard brightness, etc. controls)
- Absence of Home, End, Insert, PgUp, PgDown keys
- Absence of a "right-click" button on the touchpad
- "MultiTouch" functionality on the touchpad
So at first glance these may not seem like potentially bad things. In fact! Some may even seem good!. I mean who wouldn't prefer a multitouch touchpad or the inclusion of an extra-awesome command button? But my main problem with these is how the absence and inclusions of these features interact with the actual OS that they're intended to run on; OS X.
First off, the command button has been notorious ever since the Mac's came out. It essentially replaced CTRL for any keyboard shortcuts. Now any time I do any normal operation such as cut, paste, copy, select all; I now have to say to myself "oh, that's right command plus whatever key I was going to hit. It's really a minimal problem but when you're switching between windows and OS X, it makes life that much more annoying.
Secondly! Where are my home/end/pgup/pgdown keys!? I realize function up, down, left and right basically accomplish the same things in most mac supported programs, but there's definitely a handful that I use on a daily basis that this can get annoying with. For instance, any time I've ever used a terminal, pgup and pgdown have always scrolled the terminal buffer. For some reason messing with my terminal settings I can still only get my mac to scroll the actual terminal scrollbar, and not the buffer*. How lame is that!
Lastly, I'm just gonna throw these all into one list quick...
- F<key>'s should be F<key>'s by default. Not a "dashboard" or "next track" key by default. I need my F<keys>!
- Right click - seriously... no button? Yeah, ctrl click is a right click; but what about in my windows VM!? Now it's that much more painful to multiple select options in a box. What's even better is using the "two-fingered"** approach to emulate a right click in bootcamp. Not a fan.
- Multitouch - as cool as it is, occassionally this can get in the way as you're accidentally moving fingers around the pad or possibly pressing too hard. It's not too uncommon for me to have an accidental scroll here and there. The scrolling in bootcamp, although it works, is quite touch sensitive by default. I haven't looked into toning that down yet.
BootCamp
I assume if you're reading this you already know what BootCamp is, but for those not in the know; BootCamp allows you to partition your hard drive into a windows section and an OS X section. Allowing you to choose which one you boot when you start up your computer, thus BootCamp - clever. I will say that the drivers for the mac (they come on your OS X CD) for windows are fairly trivial to install, and work fairly well without messing around with stuff. Now you might be saying "You've got this great OS X action going on, why would you ever want to run windows!? Three words - Sam and Max. If I haven't already told you how great that game/series is, I'll have to do it another time. The main point being, nothing I threw in any of my VM's (Parallells, VMWare Fusion, VirtualBox) could keep up with running S&M without a) crashing or b) going too slow to play. So my answer to that was BootCamp.
Now once inside windows everything runs great, the hardware on mac is pretty good and can definitely keep up with most modern games. The problem? HEAT. Like most college laptop users I enjoy using my laptop, specifically; on my lap. I don't know how OS X can tame the wild hardware that this thing has inside of it, but I can only take about 15-20 mins of lap time when playing S&M on my lap. Even running completely idle the computer is fairly uncomfortable to have sitting around, thus making the portability value for your average mac->windows user somewhat absent.
This brings up another point. Apparently it is completely logical to have your MacBook overheat if you shut the lid. The first time I took my laptop into a meeting; I shut it, brought it over to the room, and opened it up only to find that all of my connections have been severed. Apparently by default your MacBook goes into sleep mode when you shut it... huh... I asked a few of the guys in the office about this and they said it was the preferred behavior simply because the MacBook Pro will get somewhat hot if you leave it on and the lid shut. I was somewhat floored at this statement but when in windows/bootcamp I can definitely see how hot my laptop and get, so for now I've just had to accept the fact that whoever designed this device didn't design it to leave it running fully on with a closed lid.
Development
I can't comment on this too much, as I haven't done too much development on the laptop itself (typically I just SSH into the development server and hack away), but I have experienced at least one problem. After a while I discovered MacPorts, an awesome program to install software/code just like apt-get on your favorite debian (or derivative) distribution! Awesome!. At the time I was trying to install xChat so I could hit up the latest #dojo-meeting. Anyways, upon trying to install it I had an error somewhat to the effect of gcc not found. Wha?! On a BSD system there's no gcc!? So thinking like apt-get I figured there was some sort of "apt-get install build-essential". Nope, nothing like that. Turns out you have to install Xcode, a development environment that comes on your OS X cd, in order to get gcc on your system (without compiling from source at least). Not having my CD around, I attempted to download from the site. Stopped again! Now apparently I have to sign up to be an Apple developer just to get to the download links! I'm sure I'm making a bigger deal out of this than it actually is, but at the time this was just simply annoying.
OS X Apps - iTunes, Mail and Spaces
The most of my grievances with OS X simply come from the apps and environment itself. I should probably preface this by saying I've never owned an iPod, iPhone or any other i<device> (except for an iHP-120/140, but I love iRiver!), so maybe I just don't "get" how these apps should work. Personally, I think iTunes seems like a monstorous program for just audio playback. Although over time it has evolved into an all-in-one media center supporting video, RSS and even online shopping; where is my standard standalone mp3 player? The days of Winamp and XMMS are all I'm really looking for when I listen to music, something small, lightweight and that I can just dump whatever plugins I want into. There may be some "iTunes lite" that I'm missing out on, and if someone knows where something like that is I would very much like to hear about it!
But this isn't even the worst part. So iTunes manages all of your media, awesome. There are um-teen hardware and software applications that interface with your iTunes library, great! Now what happens when iTunes destroys it's own library...? For some unknown reason my iTunes apparently loves to upgrade it's library to the newest version of iTunes, yet not upgrade itself so it can read that library; how? I have no idea. The error message is something to the effect: "The iTunes Library cannot be read because it was created by a newer version of iTunes".
The resolution for this, delete your iTunes library file, and re-import all of your 'tunes from the actual iTunes directory. This error has to be common enough to where you think you could probably write that recovery functionality within iTunes itself right? Or maybe I really am the lone person that ever receives this error because I don't know how my mac "just works". At any rate, this is very annoying and happens probably 2-3 times a week.
Mail I don't have as much
Now for my favorite part... spaces!. Ever since I've gotten into using x11 window managers "workspaces" have always been a favorite thing of mine. Split it into 4 spaces, use one for web, one for development, one for music/media and another for misc. When I saw that OS X supported this I have to admit I was pretty excited. Another thing I really like to do while developing is not use the mouse. Switching from space to space, application to application, even moving applications to spaces is as easy as 2-3 keystrokes in most x11 WM's. So let's try out spaces...
- Space to Space - check!
- App to App
- check!
- App to Space - FAIL!
Arg! So now if I want to move some media quickly into one space, or move my development into a web space; I can't! Well, that's not entirely true. Apparently you can hit F8, a dedicated key to space zooming out; click and grab an app then manually move it to a different space. Based on my keyboard complaints above do you see a problem? I now have to hit Function + Play/Pause (F8!) to get this to go. Once again I'm sure I can configure this but seriously, I would be configuring 75% of OS X's functionality by this point. So what now? Maybe we can do it with just the keyboard! Erm... no, we can't. Apparently someone thought it would be a great idea - that if you wanted to move an app from one space to another, you would click the title bar of the desired app, hold down the mouse button and then finally use the keyboard command to switch to another space. How completely ridiculous is that!?
Conclusions?
All in all the laptop isn't a horrible device. There are just enough inconveniences to make me want to look elsewhere next time I get a laptop. I'm sure I could cram lots more into this post but this seems to be enough for now. I also know a few people have been waiting to see what I put here or add their own input, so now they finally can! Eventually I may come up with some more "bad" aspects of my endeavors with the MacBook Pro at a later date, but for now I should really get cracking on some developing so I can post some blogs that aren't quite so pessimistic.
