Migrating to Openbox from Flux; Should I bother?

Question

Hello guys!
I'm a pretty happy Fluxbox user. I have my keybinds, my own custom made theme, a quite long apps file that gets everything going the way I want when I login.
Thing is, I do not use any of the things Flux has that Open doesn't, meaning the toolbar and the dock. Quite honestly, I even turned off the buttons from the titlebar (maximize is Alt+D, close is Alt+F4, why bother clicking? ) I do everything from the keyboard and use Conky for a much better looking clock.
So now that you get what kind of user I am, here's the motivation behind my question: Flux's keygrabber has been locking up on me (and taking away the menu) lately, leaving me with two options: restart X or mash my keyboard until I find a combination that unlocks it and resolves the problem.
So, do I migrate to Openbox? I like the look of it for the following reasons:
- it seems better maintained
- the configuration files seem to make more sense
- it doesn't have anything I don't need (toolbar, dock)
- is EWMH compliant
- has dynamic menus
Do you Openbox users confirm them all? Or should I stay put until either of 'em gets more of an edge over the other? Again, I want a speedy, minimalist and highly configurable mouse driven (no ion and ratpoison, thanks) window manager with sensible defaults (no fvwm, thanks).
Can anybody please help? I tend to obsess over this inane stuff, but I don't want to spend the time migrating my configs to Openbox only to find out it's exactly the same.

Answer 1

Alright, after the positive responses I gave Openbox a shot. Not expecting much, I copied my key bindings over from fluxbox, I figured that having gmrun as my trusty companion, everything would be fine from there.
First comment: Wow, this really feels snappier. It seems to be a somewhat faster to switch between desktops now. Anyhow, there's probably no way to realistically measure this, so this shouldn't be treated as hard evidence.
I have two and only two problems with Openbox so far:
1) Media keys don't work. Traditionally I use xmodmap to bind them to X86Audio[Play|Stop|Mute], and then Fluxbox to bind them to mpc [toggle|stop] and amixer sset and so on. I've checked xev and the keys are binded fine, what's going on then? I've bound them in my rc.xml as follows:
<keybind key="XF86AudioRaiseVolume">
<action name="Execute"><execute>amixer sset PCM 1+</execute></action>
</keybind>
<keybind key="XF86AudioLowerVolume">
<action name="Execute"><execute>amixer sset PCM 1-</execute></action>
</keybind>
<keybind key="XF86AudioMute">
<action name="Execute"><execute>amixer sset Master toggle; amixer sset PCM toggle</execute></action>
</keybind>
<keybind key="XF86AudioPlay">
<action name="Execute"><execute>mpc toggle</execute></action>
</keybind>
<keybind key="XF86AudioStop">
<action name="Execute"><execute>mpc stop</execute></action>
</keybind>
<keybind key="XF86AudioPrev">
<action name="Execute"><execute>mpc prev</execute></action>
</keybind>
<keybind key="XF86AudioNext">
<action name="Execute"><execute>mpc next</execute></action>
</keybind>
<keybind key="XF86WWW">
<action name="Execute"><execute>firefox</execute></action>
</keybind>
2) Startup of programs and automatic placement. When Fluxbox starts it starts 8 copies of urxvtc. 4 in desktop 0, 4 in desk 3. They're placed by the pixel in relation to the corners of the screen. I do this through the apps file like so:
[startup] {urxvtc}
[app] (urxvtc)
[Position] (LOWERRIGHT) {180 78}
[Deco] {TINY}
[Workspace] {0}
[end]
Picture 8 of these plus the entries to lauch Firefox and Thunderbird on their desktop, Gaim in another and ncmpc in another. How do I do this in Openbox? I could migrate the actual running of the programs to .xinitrc, but the placement is even more important than starting the applications.
So, to sum it up: help!