Mac OS X Lion

I, like so many others, decided to update to Mac OS X 10.7 (Lion) on release day. So far, its been mostly a smooth ride, but there were a few hiccups along the way. So, for my first few hours quick review:

The good:

  • Almost all of the applications I use on a daily basis seem to work just fine, including Sonatina (and amazingly Xcode 3.2 still seems to work)
  • Everything seems just as snappy as before, maybe even a bit more snappy than it was
  • Logs of the previous sessions in Terminal are a nice touch
  • Terminal in all its full-screen glory!

The bad:

  • NTFS-3G is freaking out at me on every boot. I’ve just disabled it for now, because I’m too lazy to figure out why its doing what its doing (its not an issue with the 64-bit kernel, since I was running that in Snow Leopard too).
  • The Mac App Store has been rather slow all day, so I can’t install Xcode 4.1 yet (Xcode 3.2 still works, but Xcode 4.0 refuses to start on Lion)
  • Scrolling acts contrary to what one normally expects on a normal OS (much like it does on multi-touch smartphones). Not really a big problem, but does take a bit of getting used to.

The ugly:

  • Applications that ignored Apple’s UI guidelines before or ignored the correct APIs or something that act strange… Like Firefox (note the scrollbar on the right).

All-in-all, I’m fairly satisfied so far. Dunno how much I’m going to hate the autocorrect that seems to have been brought over from iOS…

This entry was posted in Uncategorized. Bookmark the permalink.

2 Responses to Mac OS X Lion

  1. Len says:

    How is IPv6 behaving for you with 10.7? I regularly access remote hosts that are V4/V6 dual stack and my 10.7 machine will sometimes access via V4 and sometimes v6. All other machines on this LAN (iOS 4, OSX 10.5 and 10.6, XP, Win7; all dual stack) always access via v6. Strange…

    • BlueCrab says:

      I personally haven’t had any issues, other than the fact that 10.7 seems to by default use temporary IPv6 addresses (as is specified in RFC 4941), which I wasn’t expecting.

Leave a Reply

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