I've been wanting to either try or switch to FreeBSD for a while now, and I've finally done it. So far, it's great. Anybody else like or prefer FreeBSD?

Thats great, I hope you have lots of fun. I myself always looked at FreeBSD as an alternative to Linux. Of course I wouldn't mind supplementing my Linux with FreeBSD. I can't see myself ever leaving Linux, but that is because of Slackware (Praise Bob!).

Just out of curiosity though, you switched to FreeBSD from what? Windows? Or Linux?

I was using Ubuntu, then I switched to Slackware, and I just switched to FreeBSD. At first I didn't know how to install it exactly and after trying a couple of times and not being sure I was doing the right thing (or not being able to do the right thing), I just went back to Linux.
Right now I need to learn a lot about FreeBSD, but once I do I'll definitely dual-boot FreeBSD and possibly Slackware.
I've installed several distros of Linux, but settled on Ubuntu because it was so easy and then switched to Slackware because I like it more. But right when I really got used to Slackware, I decided to come back to my FreeBSD CD and see if I could get it working. It's really easy, I was just not sure what to do before.

Damn. The FreeBSD folks are really on top of things. I'm only going from 7.2 to 8.0.

Well from Ubuntu to FreeBSD is kind of a steep learning curve (unless you go with PC-BSD), but not so with Slackware to FreeBSD. Both use ncurses for the setup, however the ncurses menu on FreeBSD is a bit more in depth. The only thing I don't like about the menu on FreeBSD is the colour scheme, the text on the Slackware ncurses menu is much easier (for me anways) to read. The partitioner on FreeBSD takes a little to get used to, but not all that scary or complicated either.

My only problem with getting it set up (at this point) was I wasn't sure how to configure X.org and set up Gnome. But everything is very well documented, and I just used Lynx to read the documentation from the FreeBSD site and set those up. Basically everything else I knew this time, but the last time I tried to install it (right after I burned 7.2) I didn't really know what I was doing. I just used the livefs.iso and installed from FTP. It required a little more reading than Slackware for me, but not very much at all... I doubt you'd have problems with it (the only difference in knowledge for me really, was like I said... X.org configuration - so if you have no problems there you're probably fine). The biggest hangup was Slackware has xorgsetup, and that's what I used to set up X.org because it's so simple and quick, but for FreeBSD I had to use Xorg -configure and then I just added my DefaultDepth 24 and monitor HorizSync and VertRefresh info. Then Gnome is very easy to configure to run at startup.
I have experience using fdisk, I'm very comfortable with it... but their partitioning menu layout and everything is strange at first - but explained while you're partitioning. For the partition layout, I just chose automatic and let it set them up for me because I'd rather make 100% certain that I'm doing the right thing. Usually for Linux, I just use /, /boot, and swap. But I haven't read much about FreeBSD yet because I've been planning on reading more about it once I could get it installed easily. So far it's great.
Edited.

Yea thats another thing, the FreeBSD Handbook is very well done. So is the Slackbook, but it is a bit outdated, but overall still covers the majority well still.

One thing I liked about FreeBSD when I inherited it here was that it has a way to create an install bundle from software previously installed so you can use the bundle to install the same thing on another server.

I don't know of any other UNIX or Linux that has that built in (though of course there are ways to do something like it if you don't mind jumping through hoops).

One thing I didn't like was the way it just goes ahead and installs updates from ports for all your packages when you want to update something - I'd prefer it asked if I wanted to do that.

There are ways to pick and choose what you update and install... I haven't been reading about it for too long, but you can use ports and compile things yourself, etc.

Yea what the OP said. I am sure there is a way in FreeBSD to 'blacklist' stuff you don't want updated automagically.

I know if you use freebsd-update, you can configure it using a configuration file...I don't know. I'm 100% sure you can blacklist or whatever, somehow.

Maybe but it was a nasty surprise when I was trying to install one package and it updated Perl on my system without asking if I wanted to do it. Suddenly having your monitoring system go down because it is running software older than dirt (I've since upgraded) is a rather visible way for the rest of the organization to see there's been a oopsie.