Sunday, October 31, 2004

 

Microsoft Wireless IntelliMouse Explorer

After using with the single-button mouse for a almost a month, I've switched to the Microsoft Wireless IntelliMouse Explorer. I've concluded that the single-button mouse is obsolete, and it is just arrogance and stubbornness that cause Apple to stick with it.

I've used the Microsoft mice on Windows machines for a while. Logitech and Kensington have some acceptable models, but the various Microsoft mouse products always feel best in my hand.

I initially looked at the Microsoft Bluetooth mouse, but it was $80 and it wasn't clear whether it would work with my iMac's built-in Bluetooth transceiver. I found the Wireless IntelliMouse Explorer marked down to $30, so I snapped it up.

I have immediately noticed a difference in how easy the Mac is to use. This is not simply a matter of familiarity with a two-button mouse. With the new Macs' large screens and increasingly complex user interfaces, selecting menu items from the pull-down menu at the top of the screen or Control-clicking something is much more cumbersome than simply right-clicking something. Similarly, it is much easier to scroll with a wheel than it is to move the mouse all the way over to the scroll arrows.

The IntelliMouse control panel allows a wider range of mouse tracking speeds. I find Apple's mouse to be too slow, even at the highest setting. Neither Microsoft nor Apple provides good acceleration behavior, allowing fine control when the mouse is moving slowly but also allowing quick movements across the screen. This was once a feature that made the Mac more usable than Windows, but Apple forgot to include it in Mac OS X.

Apple once had the best mouse for any platform. This is no longer true. My Christmas wish is that Apple will develop a two-button scroll-wheel Bluetooth mouse. Until that happens, Microsoft will keep yet another foothold on my Mac.


Saturday, October 30, 2004

 

Virtual PC 7 for Mac

I received Office 2004 Professional for Mac a couple of days ago. I haven't felt like searching around for my Office 98 CDs (which I assume will be needed for installation of this upgrade version), so I haven't tried Office on the Mac yet. I was entertained by the packaging, which was designed to appeal to the dreamy stupid hippie-geeks that Microsoft believes Mac owners to be.

I did install Virtual PC 7, which is in a separate package from the rest of the Office install. Installation was easy, including automatic set up of a Windows XP Service Pack 2 virtual machine. This was a nice surprise: at work I've had to set up a few Virtual PC virtual machines on Windows boxes, and I've found that doing a full installation of an operating system on a virtual machine takes a very long time and can be problematic when the OS installer doesn't automatically recognize the virtual devices.

The first things I did after getting VPC installed were to try Windows Update, and to try to activate Windows over the Internet. Neither operation worked due to connection errors. I tried disabling the firewalls, but that didn't help. (BTW, when VPC is running, you no longer have access to the built-in Apple firewall.) What finally worked was to change the VPC network settings from "Shared Networking" to "Virtual Switch", which gives the virtual machine its own IP address. There were warnings that Virtual Switch might not work with a wireless network connection, but it is working fine for me and my AirPort connection.

VPC seems to be well behaved. When it is idle (that is, when I'm not "doing something" with the virtual machine), it uses between 2% and 12% of my Mac's CPU. Even when it is busy, it doesn't bog down my other running Mac apps.

There is a lot of integration between the virtual machine and the rest of the Mac. For example, you can drag files between the Mac desktop and the Windows desktop. Windows processes show up in the Mac's Activity Monitor process list, and you can Quit or Force Quit the Windows processes from the Mac. Windows things show up in the Dock. I'm not sure whether I like these features. I supposed they are helpful for people who need to use both Windows and Mac OS X to get things done, but I worry that VPC might be making my Mac less stable and secure.

Unfortunately, Virtual PC is really, really slow on my iMac G5. I didn't expect it to be speedy, but it is too slow to be useful for anything. So when I want to run Windows apps from my Mac, I'll use Remote Desktop Connection to access the real Windows PC that is in the other room. When I have some free time, I'll try installing Fedora, Gentoo, or one of the other Linux distros to see what kind of performance I can get from a less-bloated OS.


 

Screwed by FileMerge

While adding support for stored preferences to Rouser, I realized I needed to add another outlet to my controller class so that it could restore the setting of the on/off radio buttons. So I went into Interface Builder, added the outlet, and told it to regenerate the class files. When prompted, I clicked the "Merge" button to indicate that I wanted the new code merged into the existing files, instead of overwriting the files.

The FileMerge application started, and the windows opened. As I've done before, I just looked for "0 conflicts" and then did a Save of the files. (I ignore all the shaded curvy lines and arrows on the FileMerge display, because I don't understand what they mean.)

BZZZT! It didn't merge. It just overwrote my class files with a bunch of empty declarations. Intuitive, forgiving interface, hah!

I commit to CVS pretty often, so this wasn't a disaster. I suppose I really ought to read the docs for FileMerge one of these days. But why doesn't this do the right thing by default? You know, like a Macintosh would.


Friday, October 29, 2004

 

Rouser

My "Rouser" alarm clock application for Mac OS X is coming along nicely. It is basically functional now, allowing me to turn the alarm on and off and set the alarm time. When it is on, it displays a countdown (e.g. "Alarm will ring in 2 hours, 13 minutes, 12 seconds") that updates once per second. When the alarm goes off, it repeatedly speaks the current time ("The time is 12:49 PM.") for a minute or until the alarm is turned off.

I am using the "Bells" voice to speak the time. This sounds like a grandfather clock's chimes, emphasizing the clockiness of the application. I couldn't find anything in Apple's current documentation about the special delimiters one can use to control the voice (for example, "[[slnc 1000]]" to pause for a second, or "[[rate -10]]" to slow it down), but I was able to find plenty of unofficial information around the web. Interestingly, the most informative sites were by Newton enthusiasts. Once I knew what to look for, I did find some info on embedded speech commands in Apple's online Inside Macintosh: Sound.

There are just a few little things I want to add to Rouser before I can call it "finished":

I currently have three pop-up menus to choose the time: the first has the numbers 1-12, the second has the numbers 00, 05, 10, ... 55, and the last has "AM" and "PM". This allows me to set the time fairly quickly, without using the keyboard. If I still feel ambitious after "finishing" the application, I'd like to implement pie-like menus for the numeric fields.

So far, I'm pretty impressed with Interface Builder and the Cocoa API. Everything I've wanted to do has been pretty simple to implement. If I wasn't learning OS X programming while implementing Rouser, I think I could have put the whole thing together in less than an hour.

The only gripe I have about Cocoa is that the date/time classes don't seem to provide any easy way to extract the current hour, minute, and second. So I had to fall back on the standard C time() and localtime() functions, which aren't described in Xcode's documentation. Apple clearly wasn't considering the needs of alarm-clock developers - this is more undeniable evidence of Apple's irrational anti-alarm-clock bias.


Thursday, October 28, 2004

 

Living in Squalor

A few weeks ago, after watching the film Supersize Me!, I stopped eating fast food. I was preparing my own meals, using fresh ingredients. I felt better, lost some excess weight, and had more energy. Unfortunately, with the long hours and stress at work recently, I've returned to the old two-value-meals-a-day diet. I don't have time to shop or cook, and that fast food tastes really, really good.

This means I now bring home a couple of fast-food bags per day, along with all the excess packaging. My trash can at home is pretty small, so I developed the habit of stacking the fast food bags neatly next to it. Every few days (when I remember) I put all the trash in a bag and haul it out to the dumpster.

It seemed like typical bachelor behavior. But this morning, while going into the kitchen to make coffee (another habit I thought I'd broken), it hit me: I've got garbage piled up in my home!

Ewww.


Wednesday, October 27, 2004

 

iPod Photo

It seems that every Mac-oriented RSS-enabled site has a story today about the Apple iPod Photo: an iPod with a color screen and the ability to browse and sync photos as easily as one does with music. Many observers see this as the Next Big Thing from Apple.

I don't get it. Really, I am totally without a clue here. Can somebody explain to me why anybody would want such a thing?

A little music player that can hold several days' worth of music makes sense. This is something that is obviously useful to those who can afford it. But are there really any people out there who want to squint at tiny digital photos while they are away from their desks?

The only feature that seems useful is the TV-out, allowing one to view pictures on full-size screens and projectors. It would be nice to be able to give a presentation without dragging a laptop around.

Still, I don't see a big market for this. I have a digital camera, I play with Photoshop Elements, and I'm considering buying a digital video camera. Putting pictures on my web site and e-mailing them to friends is fun. But I can't understand why anybody would want a bunch of pictures on their iPod, taking up space that could be used for more music.

I hope I'm right. If iPod Photo takes off, we'll all have to sit through a lot of boring slideshows when the relatives visit.

[UPDATE: I'm not alone in my opinion. Here's a great quote from Paul Boutin at http://slate.msn.com/id/2108707/: "The 2-inch color screen isn't the start of any digital revolution—all it does is turn your iPod into a camera phone that can't take pictures or make phone calls."


Tuesday, October 26, 2004

 

Little Victories and Little Celebration

We passed a significant milestone today at work: we finally got all the hardware together and loaded the current software on it. And whadya know: the damn thing actually works!

This should have made me feel good, but it really didn't. For one thing, I was tired: it was after 9PM when I finally got it all working. For another, I was alone: everyone else had been gone for hours, so I couldn't share the victory with anyone. I just sent the project manager an e-mail, packed my bag, went home, and fell asleep on the couch like any other evening.

Seeing it all put together and working, I wondered "so it took five months to do this?" The system is conceptually very simple. What it does, when it works, is almost trivial. What took a lot of time was designing and implementing all the error handling for the situations when it doesn't work. You can't see any of that complexity from the outside; it's just a black box that does almost nothing, and that's exactly how I saw it tonight.

Is there something wrong with me? I'm rarely proud of my work. I never feel a sense of accomplishment. I focus more on what I didn't do, or did poorly, than on what I did well. So work is just a series of disappointments.

How can I turn this around? Is it the nature of the work, or just my own nature? If it's my own nature, can I and should I change it?


Sunday, October 24, 2004

 

Two Weeks In

10:42  up 8 days, 21:46, 3 users, load averages: 1.56 1.41 1.14

The iMac has been pretty stable, after the first few days of instability. I haven't had many application crashes (only OmniWeb is prone to die) and haven't needed to reboot.

While the iMac experience is generally good, I do have a few minor complaints:


Tuesday, October 19, 2004

 

Application Naming

I've read a few chapters of some Cocoa programming books and documentation, so I'm ready to start work on my simple Mac OS X alarm clock application. The first step, which often takes me longer than the actual implementation, is to come up with a cool name for it.

I could just call it "Alarm Clock", but that would show a lack of imagination. I did Google searches of some synonyms and related words, like "Alarm Time", "Wake Up", "Alarmist", but all were already used by someone else's alarm clock application. I also looked into some alternate spellings, like "Alarm Clok", but again, somebody else had the same idea.

I considered some platform-specific names, like "Cocoalarm", "Aqualarm", and "Alarm X", but all those were already in use or they put me at risk of legal action from Apple. (If those %$#@ers at Apple hadn't removed the good-old Alarm Clock desk accessory from Mac OS in the first place, none of this would be necessary.)

"Strawberry Alarm Clock" is a cool name. But I think it's taken.

I've released some freeware under the fictitious business name "Sleepless-Night Software". "Sleepless-Night Alarm Clock" does have a certain ring to it, but would be too big for the application menu title.

So I'll keep thinking about names. I can't start the work until I've got a good one.

[UPDATE: I've settled on the name "Rouser". Until I think of something better.]


 

I Bought Microsoft Office for Mac

I just ordered Microsoft Office Professional for the Mac. I feel a little dirty.

I was hoping that the Mac could be a Microsoft-free haven for me. Then I found that I needed Windows Media Player, so I got that. Then I needed Microsoft Remote Desktop Connection, so I got that. Then I needed MSN Messenger. But those were "free", so I consoled myself by thinking that at least I wasn't giving any more money to Microsoft.

Unfortunately, I can't find a good substitute for Microsoft Office. OpenOffice for Mac is uglier than any Windows application I've ever seen. AppleWorks feels like a toy, and can't read Office file formats. When I brought work home, I wanted to use the Mac, but couldn't.

What finally drew me in was the announcement that Virtual PC 7 would be included in MS Office Pro. I don't really need to run Windows on my Mac, but I would like to try out Linux distros and other operating systems.

The last Office version I bought was Office 98 for Windows. That qualifies me for the upgrade price, so I'm getting Virtual PC and the rest of Office for a little under $300. That's a pretty good deal in the Windows world. And maybe it won't suck quite as much on a Mac.


Sunday, October 17, 2004

 

Sprinting to the Finish

I haven't written much in my blog about what I'm doing at work. This is because I've wanted to avoid writing anything that could get me into trouble with my managers, coworkers, or customers. However, I do want to write a little about what's going on at work, because that is what I'm spending most of my time thinking about. So I'll write, but I'll have to leave a lot of the details out.

We're approaching the deadline (Nov. 15) for getting our system installed and operational at the customer site. This is a hard deadline; it absolutely cannot slip beyond that date. Software-wise, I think we're OK. The problem is that we don't have many of the the custom hardware components that will make up the production system. The software works great with mock objects taking the place of the hardware, but until we test the system with the actual hardware, we won't really know if everything works.

Integration testing is starting tomorrow, so I'll be in the office this evening putting the final touches on the test environment. Hardware components will be showing up during the week, so I expect many long hours of hooking new things up and figuring out why they aren't working.

It is too early to really know what we did right and what we should do differently next time, but I've already started my lists:

What we did right:

What we didn't do right:

The code that we have developed for this project is supposed to become a new framework to be used for developing similar systems. I already expect a lot of resistance. We have a lot of decoupling between different subsystems, which leads to more flexibility but also makes things look very complicated in comparison to the older codebase. There are some things that could be made simpler, so I hope to have some time to clean those things up before presenting the new framework to others in the software development group. I know they are going to hate it, but I'm not going to worry about that.

There were a few weeks in the middle of the project when I got a little depressed and burned out. We weren't getting the information we needed on hardware, our project manager was re-assigned to another project, and I felt that it was up to me to fix every problem myself. Thankfully, I got past that by allowing myself to focus just on what I could do and to stop worrying about what I couldn't do. Now, we've got a month to go, and I am pretty optimistic about how things will turn out.

When it's over, I'll allow myself to finally take a vacation. I haven't had any time off since I joined the company 15 months ago. Not taking any vacation has probably been my biggest mistake.

After some time off, I'll have to do some heavy thinking about what I want to do with my career. This recent project experience has given me more insight into how the company works and how its management does things. I have more data to consider as I decide whether this is where I want to stay for a while, or whether it is time to move on to something else. At the moment, "something else" is very attractive, but I don't know how I'll feel after the project is behind me.


 

Sleepless-Night Wiki Moved to Quartus

A few years ago, I created the Sleepless-Night Wiki as a forum where Quartus Forth users could exchange information and code. I considered it to be pretty successful, as it attracted several talented people who contributed code, tips, and advice. It also attracted some people interested in related matters, such as general Forth topics and Palm OS issues. Sleepless-Night was based on the TWiki software.

Earlier this year, the wiki went down when my evil hosting provider moved all my files to a new differently-configured server. It stayed down for several months, as I couldn't get FTP to work and every attempt to use the "web control panel" provided by the hosting company made me give up in frustration.

Getting the Mac prompted me to approach the problem again. This gave me a chance to try out different Mac web browsers, FTP clients, and Internet utilities. I got the wiki mostly working again, although I didn't get around to re-implementing the authentication mechanism.

As most of the wiki content is related to Quartus Forth, and I don't do anything with that tool anymore, I've transferred all the wiki content over to Neal Bridges at Quartus. The new Quartus Wiki can be accessed at http://quartus.net/wiki/. Everyone's old passwords should still work.

The wiki contains a lot of info on personal projects of mine. I'll probably set up a Sleepless-Night Wiki Mark II as a repository for those things. UseModWiki is the wiki software I like now; I used it to set up the Remoting.Corba Wiki and a few other private wikis. TWiki has a lot of features, but it was always a little too complicated for users to figure out.

Unfortunately, there are bots out there that add wiki-spam to UseMod wikis, so I'll probably have to make my wiki read-only for everyone but myself.


Saturday, October 16, 2004

 

The Brushed Metal Look

I was going to blog about what I think about the mixture of the "brushed metal" look and the more traditional Apple look in Mac OS X, but someone else already wrote everything I wanted to say: http://daringfireball.net/2004/10/brushedmetal.

The Finder is especially annoying in that it switches itself between brushed metal and plain-old-window depending on whether you show or hide the toolbar. With the Apple Human Interface Guidelines encouraging developers to look to the Finder as an example of correct UI design, it's not surprising that people can't agree on the appropriateness of the brushed-metal look or on many other aspects of how a "real Macintosh application" should work.

I don't understand why Apple wants its applications to look like a bunch of overpriced components for audiophiles.


 

The One-Button Mouse and Where to Put My Fingers

The Mac still ships with a one-button mouse. This made sense to me back in the System-6-and-earlier days. Other operating systems had confusing and inconsistent uses for their multiple mouse buttons, and Apple's solution seemed to be the simple and elegant one. Apple's one-button mouse was easier to use, and also of much better quality than the cheap multi-button mice that were shipped with PCs back then.

Things are different now. Other operating systems introduced the right-click context menu; Apple responded by using a Control-click. This has become clumsy. The context menus have become the primary means of controlling a lot of on-screen objects, yet Apple insists on this two-handed method. It's too bad, because I really like the look and feel of the Apple Bluetooth mouse; I just want another button (and maybe a scroll wheel).

I know I could just take the easy way out and buy a third-party multi-button mouse, but as an experiment I am going to stick with the one-button mouse. Maybe I'll get used to it. Maybe I'll develop carpal tunnel syndrome. I just want to see if maybe Apple's UI designers are on to something. (Although I wouldn't be surprised if all Apple's UI gurus have multi-button mice.)

All this use of the Command, Option, Control, and Shift keys along with the mouse, as well as my increasing use of keyboard shortcuts to avoid the mouse, has made me start thinking about exactly where I should put my fingers on those keys. When I took typing class back in high school, I learned to use my right thumb on the spacebar and my pinky on the Shift key, but they didn't have these extra keys back then. I've been sloppy, just hitting keys with whatever finger happened to be closest, but I think I may be more efficient and less likely to suffer from RSI if I can touch-type the modifiers like I do the rest of the keyboard.

Should I press Command with my thumb, my index finger, or my middle finger? Should I press Control with my pinky, or with my ring finger? When I use a shortcut like Command-Q, should hit both Command and Q with my left thumb and middle finger (which is the habit I've developed), or should I hit Command with my right hand and Q with my left (thus avoiding a weird stretch of the hand)?

I've decided, for now, to try to consistently use my thumbs on the Command keys, index finger on Option, and ring finger on Control or Shift (and if I have to hit both Control and Shift, use index on Control and ring on Shift). I am used to using my thumb for Command, so I think this will be an easy habit to develop.

The harder challenge will be to break my habit of one-handed "chording"for Cmd-Q, Cmd-Tab, Cmd-S, and other common shortcuts that are possible with the left hand. When I use the Shift key, I have no problem using two hands, so I hope I can develop the same habit for Command.

Maybe I should just buy a new mouse.


Thursday, October 14, 2004

 

iMac Memory Upgrade

I added 1 GB of RAM to my iMac, bringing the total up to 1.5 GB. It is much more responsive now. Applications launch faster; the Dock pops out instantly when I put the mouse in the right place; windows resize without all the jerking around; Exposé is smoother.

If I had it to do over again, I would have ordered the iMac with the minimum RAM (256 MB), then bought 2 GB of RAM from some place else. Crucial will sell 2 GB of Mac RAM for $505. In contrast, Apple adds $1,225 to the price tag if you want 2 GB out of the box.

Performing the upgrade was easy. I did some bad things to the screws when opening up the Mac. I was expecting them to come out when I unscrewed, but they are captive screws that stay in place when you turn them. So I ended up unscrewing too far, and turned the Philips slot into a conical pit. Don't make this mistake if you do this yourself.


Wednesday, October 13, 2004

 

Emacs for OS X

One of the first things I wanted for my Mac was a good text editor. TextEdit is okay for simple tasks, and I can use vi in a pinch, but I really wanted something like Emacs.

So I started searching for Emacs/XEmacs for OS X. I found about a dozen different builds from different sources. Some ran on X11, some ran only in the Terminal. Some were relatively new (Emacs 21); some were pretty old (Emacs 19).

The best one I found is a Japanese-built Carbon Emacs Package. This one is built from the current sources in the Emacs CVS repository, and doesn't require an X11 server.

One problem with this version is that font support is bad. The default font is a big Monaco font. I tried changing font faces, but always ended up with something worse than the default (which is ugly). This package is apparently designed for Japanese users, and the Roman font support just isn't there. Every attempt to use the Set Font/Fontset command results in a "Font not found" error, and attempts to use the Customization screens result in something uglier than the default. I decided that I can live with the default font.

There are some non-Japanese builds of Emacs with Carbon floating around, so I'll give those a try. Eventually, I'll overcome my natural laziness and figure out how to build it myself.

By default, the Command key is used as the Emacs Meta key. I prefer using the Alt/Option key, so I added this to my .emacs file:

  (setq mac-command-key-is-meta nil)

Tuesday, October 12, 2004

 

AirPort Card Freak-Out

Last night, for no apparent reason, I suddenly lost the WiFi connection on the iMac. I was unable to access the Internet or the other machines on my home network. Every attempt to reconnect to the network gave me an error message. My other laptop with WiFi was working fine, so I assumed it must be an iMac problem, but I tried re-booting the wireless router anyway. No help.

So I re-booted the Mac, hoping that would fix it. Nope: still unable to connect.

I tried re-booting a couple more times, along with various other acts of desperation. What finally fixed it was a full shutdown and restart. After that, everything was fine.

I'm finding that I have to reboot or shutdown-and-restart my iMac a lot more often than I do with my Windows box. I'm hoping that trend will change once I get through the initial shakedown period.


 

Alarm Clock

One of my favorite desk accessories on the old Mac was the Alarm Clock. Mac OS X doesn't have one. Neither does Windows. I miss it.

I don't know why it disappeared. I guess they figure the appointment-setting features of iCal, Outlook, or Entourage eliminate the need for a simple alarm clock. But they don't: I often want my computer to remind me when a TV show is coming on, or to check the oven in ten minutes, or for other impromptu events, and I don't want to go through the whole process of creating an appointment (specifying date, time, length, location, who's attending, etc.).

I found a few alarm-clock utilities for OS X, but none of them do exactly what I want, and the more useful ones are not free. So I may need to write my own alarm clock application. This will be my chance to learn to write a Cocoa app.

In the meantime, I'm just going to use the UNIX 'at' command from the Terminal to trigger the speech synthesizer. I can use it like this:

localhost:~ kdj$ at 13:50
say -v Vicki 'Kris, it is time to go back to work!'
^D

and then a soothing female voice will gently wake me from my afternoon nap.

If you decide to use 'at' yourself, be sure to read the man page for at. It is necessary to enable the 'atrun' command in /etc/crontab before it will work.


Sunday, October 10, 2004

 

iMac First Impressions

My iMac arrived a few days ago. I took it out of the box, put batteries into the Bluetooth keyboard and mouse, plugged the power cable in, and turned it on. I was pleased to hear the good old Mac startup sound, although it was startlingly loud.

Going through the initial startup screens was pretty easy. The only snag was that I couldn't figure out how to enter the WEP key needed for the AirPort card to connect to my wireless network. So I went without network access at first, then I just disabled WEP on my router so that I could test Internet access and download updates. Later, I found out that it was necessary to enter a '$' in the AirPort password field before typing the WEP key. Once I discovered this little tidbit, I was able to restore WEP.

I last used a Mac in the System 7.5 days. It is interesting to note what has changed, and what is the same. OS X has much more support for keyboard navigation than the old Mac OS had. The top-of-screen menu bar looks familiar, yet has standard menu items in different standard locations.

The new Finder is very annoying in comparison to my memories of the System 6 and 7.5 Finders. The windows and icons are too big to see everything I'd like to see at one time. Too much valuable screen space is used by the brushed-metal title bar and toolbars, and it seems to be too difficult to do simple things. Is there a good reason that the Finder will let you use Edit->Copy to copy files from place to place, but won't let you use Cut and Paste to move them? The Finder's handling of FTP servers and Windows shares really sucks. I've had the Finder lock up, and it was unable to restart when I used Force Quit on it, so I had to reboot. All in all, I think the Mac OS X Finder is the most Microsoft-like of all the Mac's features.

I am getting used to the Dock. I found it a little confusing at first, but now I prefer it to the Windows status bar mechanism. After playing with a few configurations, I settled on auto-hide on the right side of the screen: it is easier for me to flick the mouse to the right than down to the bottom, and this puts the Trash down in the lower left corner of the screen (as God intended). I would like to have a menu of all open applications on the system menu, like 7.5 had, instead of needing to use the Dock or Command-Tab to get to other apps.

Exposé is the coolest new feature. For those of you who haven't seen it, it shrinks all your windows and tiles them so that you can see them all at once and select the one you want to see. It is not just a thumbnail-like mechanism: while shrunk, the windows are still updating (you can see web animations, or terminal windows scrolling). I predict Microsoft and other OS vendors will be providing similar mechanisms soon.

None of the Mac web browsers are as nice as Internet Explorer on Windows XP. OmniWeb and Safari are both OK, albeit a little less "snappy" than I would like. Firefox is slow to render, and doesn't have a lot of the standard file associations built in. I'm sticking with OmniWeb for now.

Here are some other applications that I've settled on:

As I have a couple of Windows machines at home, I spent a lot of time with Mac OS X's support for Windows file and printer sharing. I am not impressed. It works well when everything is set up correctly, but if I reboot my Windows box while the iMac has a share open, or at other random times, the Finder will completely lock up. I have since given up on file sharing, and I now use FTP to transfer files between Mac and Windows.

I was eventually able to get my iMac connected to my HP DeskJet 5550 printer that connected to my the Windows XP box, but fumbled around for a while because the huge list of HP drivers in the Printer Setup dialog doesn't include the 5550. I eventually decided to use the "dj450" driver (which I vaguely remember from setting up CUPS on a Linux machine), which seems to work although I get edges cut off on some printed pages.

I downloaded Microsoft's Remote Desktop Connection software for Mac. It works very well. As my Windows box is in a different room from my iMac, it is nice to be able to remotely control Windows when I need to find a file to be transferred, or check what my password is for some web site, and so on.

I keep hearing about how the new iMacs are completely silent. Mine is not. It's not loud, and it's not annoying, but it is not silent. I assume the sound is a fan, a disk drive, or both.

Despite the minor annoyances listed above, the iMac has quickly become my primary machine. I only turn on the Windows box if I need to move an old file over or to use the RC helicopter simulator (for which there is no Mac equivalent). It's not that the Mac is better than Windows XP; it's just different, and being able to escape from Microsoft when I leave work is a nice thing.


This page is powered by Blogger. Isn't yours?