I'd definitely consider using a Chromebook if the offline functionality works. My understanding from people I know working at Google is that the offline Docs and Gmail experience is pretty sub-par at the moment.
I guess if you pop out their SSD for a larger one it'd make a decent BSD netbook. Bitrig[0] is slowly but surely getting better.
I bought a Chromebook Pixel 2015. The first thing it asks, when you turn it on, is for an Internet connection. You cannot go past the first-boot panel until you give it internet access, then agree to Google's ToS which says you'll let them auto-install updates at anytime, and then let it try to download updates from Google. Then you must log in to a Google account.
I didn't bother with ChromeOS enough to see how well offline apps work. The laptop does not have any screws, and I'm told the SSD is soldered on even if I knew how to take the laptop apart without breaking it.
That being said, there are magical keystrokes you can use to bypass even the intro "first boot" panels to switch the laptop into "developer mode" which you can use to wipe ChromeOS and install a real Linux. Much of the hardware isn't supported by mainline kernels, but Google has a lot of that sourcecode online, so I'm trying to compile my own module to get the touchpad to work in Debian.
That's all experirence with a different product than what we're talking about here, but my anecdotal observations are that ChromeOS fundamentally expects internet access, and it might not be possible to upgrade the hardware and get a comfortable setup with a real Linux or BSD.
ChromeOS devices are less "surprising" in this sense, if you think of them not as computers per se, but as (the fat-client equivalent to) thin client appliances that boot into a Citrix session connected to a machine-instance running within the Google cloud.
It's not a perfect analogy—you can use [some carefully-written apps on] the device without internet access once you've set it up, and so forth—but thinking in those terms lets you predict what ChromeOS will tend to do in a given situation quite well.
How to open the Pixel 2015: remove the two glued-on rubber strips on the bottom, remove the 15-or-so screws below them, remove the bottom plate.
Once you're there, you can even turn a screw (or pull a jumper on some devices) to unlock the write protection of the firmware flash chip.
https://johnlewis.ie/custom-chromebook-firmware/rom-download... provides tested replacement firmware that make running 'regular' operating systems more comfortable on many Chromebooks (no more security measures in the form of scary warning screens and 'return to factory' key combos). That may kill warranty - or not.
I find that this is a pretty reasonable trade off between providing an 'unbreakable' secure-by-default (hence the auto updates, which also cover firmware) configuration that is also reasonably safe against drive-by attacks (that's why the jumper is inside the device) while allowing people to use their hardware differently if they want.
This doesn't rely on security problems that are used as 'jail break' elsewhere.
And yes, the SSD is soldered on. There's not a whole lot of space in that box, and soldering makes things so much more compact.
I don't know about modern chromebooks, but I have an Acer C7 that I spent $199 on and then added another $240 for it to have a 128GB SSD, 16GB RAM, a working bluetooth module, and an upgraded battery. $440 total and it's been a solid dev machine running first chrubuntu and now crouton. I've mentioned before that the only issue I've had with it is lack of CPU horsepower for clojure-based work to get into the REPL, which as I understand, is slightly fixed on later iterations (or other models). All of my hardware (AFAICT) works under Linux, and I use Google Hangouts, Skype, Steam (for TFC), and vim/tmux on it routinely.
And I'd still need to spend another $300 for the SSD, 16GB ram, and a new battery (batteries on used laptops are miserable, and not up to the 8 hours of usage I demand). It would also be heavier.
My battery lasts about 9 hours on a charge with normal usage (testing/developing in vim with Python (using python-mode+jedi) and Clojure (using vim-fireplace and nrepl-middleware) against Postgres, Mongo, Elasticsearch, Redis, and Storm. The original battery was somewhere in the 4-5 hour range.
The offline experience is going to be pretty much what you'd get with the offline experience of those apps in Chrome on a Windows or OSX computer, so you can try it out pretty easily.
I guess my point is that people don't always have wifi. I want to use my laptop on the plane (though some airlines now offer super-exorbitantly-priced wifi, I still refuse to pay for it) or in the back seat of a car.
I should be able to tap away at a document or use a Thunderbird-style "send emails when you next have connectivity" mail client.
My understanding is that the Google apps don't currently offer this.
Try it out on your Windows laptop, if you want, and you'll see how it works. My understanding is that this functionality is there to some extent, but I haven't used a laptop without wifi in long enough that I have no real idea.
As far as I know, most Google branded apps can do this and there is nothing preventing third parties from doing it too. You can probably boot your laptop with a ChromiumOS live stick and check it out.
I haven't actually used a Chromebook but I'm surprised they're struggling with offline functionality. Android does just fine on spotty connections - at least Google's apps do - I wonder why they don't have a few mobile experienced engineers help out revamping so their apps just assume a crap connection and deal with it the same way they would on mobile.
Even then, you'll probably have a pain in the butt time. It uses coreboot to startup, and the coreboot devs don't seem to care about any OS that isn't Linux, so you have to go through a somewhat painful process to get to the point where you can install a BSD.
(wearing my coreboot developer hat): We care about BSD. And Windows. And Solaris, Haiku, and whatever else comes our way that runs after coreboot. The amount of care varies with developers, and Linux is indeed the OS that sees the most interest.
If BSD fails with coreboot + SeaBIOS, that's a bug, and I'd love to hear about it. And I think so would the SeaBIOS developer and the QEmu people who use the same PCBIOS implementation.
I guess if you pop out their SSD for a larger one it'd make a decent BSD netbook. Bitrig[0] is slowly but surely getting better.
[0] https://www.bitrig.org/