• You need to buy and install a copy of Windows XP Home or Pro. (That adds another $100 to the cost of the Macbook for most people.)
• No right-mouse-button. A work-around is to press Shift-F10 to emulate a right-click.
• Have to use a keyboard remapping utility to mak the right Apple key to Delete.
• You have to waste 20GB of your hard disk on the Macintosh partition.

Apple will probably fix the delete key and right-click issues in future versions of Boot Camp.

I will say that I very much enjoyed playing with the included Mac software -- it's quite nicely put together. I especially liked these features:

• The two-finger touch pad short cuts for scrolling and right-clicking are great. I hope they become available on Windows XP in future versions of Boot Camp.
• The ability to exactly copy a data CD without having to install a third party utility.
• The clean and simple control panel UI.
• The very nice artwork (in terms of fonts, colors, and images) included in the system.

I think Boot Camp is a two-edged sword for Apple. On the one hand it removes a huge barrier-to-entry for people who need a real Windows machine. Since that's such a large percentage of the public, I think short-term this is a huge win for Apple.

Long term, however, the picture is somewhat bleaker. Boot Camp means there is much less reason for nich or hard-to-port products to be ported to the Macintosh. The clearest example of this is games, because games have a short shelf life, and game users are technically savvy enough to install and use Boot Camp. But it also means business applications.

It will be very interesting to see if Apple ever goes to a two-button track pad, as this is the last big hardware barrier to using their computer as a Windows PC.

• I was new to F#, so I spent a lot of time stuck trying to understand syntax error messages.
• I was using a very poor development environment: notepad and fsi.exe. (F# has a good Visual Studio based development environment, but I was using a borrowed computer that didn't have VS installed.)

The F# code is shorter, and most parts of it are extremely clear and easy to read and modify. Unfortunately, some parts of the code, that I copied and pasted from sample programs, are a mess of spagetti.

F# suffers from being a second-class citizen -- almost all sample code and documentation is written in C#, so in order to use F# you have to be able to translate from C# to F# in your head. This is difficult to do when you're learning the F# language -- it greatly adds to the F# learning curve.

The next logical step is to write a slightly larger, new game in F# and see if the benefits of F# grow with a larger code base.