fluffy grue voted 1 on this story.
These are nice things to know. I'm actually a Be registered developer, but only had BeOS installed for a few months, during which time it mostly gathered dust, simply because the UI couldn't be configured for my ergonomic needs, unlike fvwm2 which allows me to tweak everything I need. In fact, I emailed some of the Be developers about this issue, and their responses were generally "I don't see why you'd need that" or "Well, you can't customize that, but there ARE themes now." Sorry, I need the ability to at least generally move the mouse by the keyboard (I have a pretty severe RSI in both hands, which is only exacerbated by switching between a keyboard and a mouse), and being stuck to a little tab for moving a window and a little square in the bottom-right corner for moving it are even worse, not to mention being stuck having to move windows to begin with, whereas with fvwm2 I set up the square edges for moving, the corners for resize (and also have convenient keyboard shortcuts for doing both), and SmartWindowPlacement.
Oops, I wandered again. Anyway. I'll have to check out the review when I get a chance; hopefully the UI is much more flexible which is, as you may have guessed, the major issue I've had with BeOS in the past - in fact, aside from the UI, I loved it, though it helps that it supports all my hardware too. :)
BTW, the only app I use a lot where I have to touch the mouse for in fvwm2 is Netscape, and that's okay since it doesn't normally involve switching between the keyboard and mouse very often. Then again, most of my other apps are terminal-based and not graphical (X11 - a nice replacement for screens :)
"Is not a quine" is not a quine.
I have a master's degree in science!
[ Hug Your Trikuare ]