A tip for first-timers: perform the installation with an Ethernet internet connection. On my laptop, wireless firmware was installed and configured automagically on first boot. After that it's all gravy.
Yes, it's much easier that way.
Then, once the firmware for your wireless card is installed, configure your wired and wireless interfaces as a failover trunk (if you switch back and forth between them very often). This way, your IP address doesn't change when you {dis}connect your Ethernet cable. Obviously, everyone has different needs but this works out great for me (I plug in when at my desk and use wireless the rest of the time).
Seems the currently recommended method is to just run dhclient on both wireless and wired interfaces and let the routing table to decide which to use.
That said. Finding pre-built binary packages can be hit or miss. And ports requires X11 to be installed.
But when all is said and done. It's the community that's most important. And OpenBSD has one of the kindest and active IRC channels on freenode. Far from the "in your face"/elitist reputation others have stated before.
Sure.. though from what I can see, openbsd didn't support wpa enterprise until 2013, and at that point it was supported using wpa_supplicant.
http://www.undeadly.org/cgi?action=article&sid=2013012814221...
I've found a great use case for it though; older, slower hardware (think P4 and older) actually benefits from running OpenBSD versus most modern Linux distros. For example, I have an ancient PIII laptop that refuses to run anything other than OpenBSD, Slackware, and Haiku OS. Out of those, OpenBSD is the fastest and least buggy. Granted, it's just a toy/hobby device, but I found it intriguing nonetheless.
http://www.laptopmag.com/reviews/laptops/fujitsu-lifebook-s7...
The above ~5yr old laptop will give 60fps running minecraft with no hiccups / glitches. Installed an SSD and frankly its a perfect workstation for anything I would use and I see no lag.
It's just laggy and runs hotter than Linux. I get a solid hour and a half more battery life on Linux too.
Obviously I reported it.
There's also a general choppiness to X itself. All of this with accelerated Intel graphics, so it's not necessarily driver related. I just figure that given the project's focus on security and clean code, desktop OS performance takes a necessary back seat.
Even with all of that, I give every new release a thorough test run on my old workstation and laptop, just to see if things have improved in that area. And they have been steadily improving!
In FreeBSD, it's powerd. In OpenBSD... apmd?
Also there was fix in ACPI in 5.8 to fix power use in newer processors. If I remember it correctly the processor didn't use the deep sleep states so they consumed more power.
You are free to search marc.info for the fruitless threads of me trying to solve multi-second system freezes when opening emacs or changing workspaces if you like.
The fact that the devs dogfood their stuff is irrelevant: it doesn't perform even remotely as well as Linux on the same (modern) hardware.
Openbsd has always felt turbo fast to me. Easily the tightest Unix experience, in my experience.