fsck? In 2008? No thanks. Messages about possibly corrupted inodes? How should that be my problem? I can't stress this enough, one day you will wake up and FreeBSD will refuse to boot. And that day will, by Murphy's Law, be one of those days where you have to get an incredible amount of real work done.
I'm a big fan of FreeBSD, ports, and the whole "do it right" and "proper documentation" philosophy. But until they get journalling right you should probably stay away.
(also: upgrading from FreeBSD 6.x to 6.(x+1) is incredibly painful. I don't think upgrading a 7.x system is going to be much easier. Reinstalling FreeBSD gets old fast, so you'll probably just shrug and stick with whatever version you already have)
There are 2 things creating problems now, though: first, it does not use journaling (by default) leading to expensive fsck times on big disks. Second, it could have faster meta-data operations.
The filesystem has a construction such that a system crash can only lead to unreclaimed free space on the disk. If that is not the case, you are facing a hardware error. The primary role of fsck is to put back this free space.
Journaling is now experimental in FreeBSD. ZFS is experimental in FreeBSD. As soon as these stabilizes, the problems mentioned here goes away entirely. Note that "experimental" means that the state is equivalent to most things linux: the crap actually works but have not yet seen the strains of time.
With FreeBSD Update, it takes two commands, "freebsd-update upgrade -r <new release>" and "freebsd-update install".
Sometimes fsck needs to run for a bit after a crash or power outage, but it has only lead to a 2-10 minute delay for me, not refusing to boot. Annoying, but hardly fatal.
Have you looked at the FreeBSD Handbook? (http://www.freebsd.org/doc/en/books/handbook/) That will probably answer many of your questions. Also, the OpenBSD FAQ: http://openbsd.org/faq/
I've used OpenBSD on the desktop and servers for over five years. I mostly use it for programming (Emacs), playing music (mpd: http://mpd.wikia.com/), and nethack. I use Firefox and w3m for web stuff, dwm as a window manager, mercurial for vc, etc.
OpenBSD's focus on security keeps the core system simple, well documented, and straightforward to configure, so as to minimize the amount of obscure things that could lead to vulnerabilities. FreeBSD is also an excellent OS, but OpenBSD's clean and minimalistic design is more my style.
I don't think it's very different from using a non ultrapolished Linux distro(like Debian). Choose your WM, install bash or (pd)ksh(tcsh sucks) and your prefered tools(Eclipse, LaTeX, Emacs, OOffice... whatever) and you're ready to work. I don't like GNU userland so for me that was a plus, but some people can't live without colored ls and a several megs vi, so your mileage may vary.
Desktop environment: KDE3.
Text editor: kwrite.
Office suite: OpenOffice.
Web browser: Konqueror for most sites, Firefox for a few sites which don't work in Konqueror.
Email: Thunderbird.
Other communications: Kopete (for ICQ), aMSN (for MSN), ksirc (for IRC).
System administration tools: FreeBSD Update for base system security updates; Portsnap for updating the ports tree; portupgrade for updating installed ports; tarsnap (of course!) for backups.
openbsd generic kernel covers almost everything i need (no bluetooth support) - for complete hw support, i use ubuntu
overall, openbsd is simpler. Last week i just upgraded from 4.0 to 4.4 on remote machine in about 2-3 hours). I never bothered to upgrade before :D 400+ days uptime is normal
for desktop, i use dwm, firefox3, mrxvt, qiv, axyftp, vifm, vim (non-gui), mpg123, mplayer, ImageMagick, gimp, lighttpd, mercurial, newlisp, tightvncviewer (to control my Mac Mini GUI remotely)
That hasn't been necessary for the past 3 years.
emacs22
Firefox
And WIN4BSD when I need to test my work in IE or other Windows browsers.
It's no different than running a Linux desktop and you are running the same software. The question is a little strange to me.