Except for the fact that developers can be productive in many programming languages on Windows, Linux, and OSX... but in order to develop for ChromeOS you are restricted to javascript alone.
That is very different from the work required to port a game from Windows to Linux, using a familiar programming language and the plethora of cross-platform UI toolkits.
Targeting ChromeOS for development is prohibitively expensive in regards to pre-existing skills. Hence it is a browser toy.
Maybe in the future ChromeOS will be popular enough that things change, but that is hardly relevant to this thread.
...
I'd just like to add that half the flaws you listed are Windows specific, the other half are imaginary.
Forced reboots are a legendary Windows thing, arcane terminal commands are a hallmark of people comparing the ease of modern Windows to the complexity of
last decade's Linux systems, and WTF defragging? That *might* be necessary according to your filesystem type -- ChromeOS doesn't have some magic no-defrag-necessary filesystem, it has the traditional linux no-defrag-necessary filesystem.
...
tl;dr
ChromeOS still isn't useful for an ebook management platform.