I purchased a chromebook with no intention of using ChromeOS on it, but tested ChromeOS on it for a weekend to get a feel for it and see if it were the sort of thing that I could recommend to family members.
(Traditionally my go-to advice has been "Get a Mac", even though I do not use a Mac, but they never listen to me...)Anyway, I knew going into this weekend experiment that it would not satisfy my needs, but I was surprised at just how shit it was. Typical tasks that my mother performs could mostly be done, but none of them could be done well. I could browse images from a camera flash card, but the image browser was absolute rubbish that anyone would hate. I could similarly view video files... most of the time, depending on the format and encoding. My mother uses VLC right now on windows, she doesn't know the difference between an encoding and a container (indeed probably doesn't even know that there is a difference), nor should she. Google has built software that can play local videos, has build hardware that can play arbitrary videos (Using Debian, mplayer or VLC run just fine), but have put together a product that has arbitrary technical limitations that my mother would not understand.
And no, the standard ChromeOS apologist shit of "You just don't understand the use case" does not apply here. Google has built a product that does provide the functionality I tested, it just does it poorly. If you are going to do it, do it well. If the OS had just flat out refused to provide me with ways to do those things, that would have been one thing, but that isn't the situation with ChromeOS.
Many of the problems with ChromeOS are not a result of limitations with the concept of ChromeOS, they are the result of a shoddy implementation of the concept of ChromeOS.
(Specifically, I purchased a Chromebook Pixel, and used the most recent ChromeOS sometime early in June of this year.)