Also I used one for 2+ weeks exclusively (running Fedora 18) and it wasn't that bad:
http://rwmj.wordpress.com/2013/01/16/some-thoughts-after-2-5...
On my Chromebook, it boots as soon as you open the lid, and so I press Ctrl-D instead of the "On" button. I thought it'd be a pain, but it doesn't bother me at all, and you say that makes it "practically useless"?
(The infuriating bit is how difficult it is to enter developer mode: two very secret keypresses and a thirty-second "please reconsider" grace period.)
I do mind having to do them each and every time I pick up the computer, especially when I have bought it believing that I won't have to.
But if you're dual-booting to another Linux distribution or just replace ChromeOS altogether (that's another issue with the linked article: what it describes is not a dual-boot) you can't escape frequent reboots. Especially due to flaky suspend/sleep mode support in other distros.
Source: The article you're commenting on
It turns on and off as normal after installation, you just need to hit Ctrl-L mid-boot each time. I reboot infrequently enough that this hasn't annoyed me yet.
You can flash the first stage bootloader to remove that warning, but that is not documented well (if you can call several contradictory forum threads documentation), involves taking the laptop apart and gives you exactly one try: it either works or bricks the device permanently.
In addition to that, at least Samsung's Chromebooks are not very well designed and can be seriously damaged from userspace when running a general-purpose distribution (Google for burning speakers on ARM Chromebook for instance)