I wonder what's the point in writing a book about Dart, where the language, environment, toolchain, compiler(s), and community are still very, very unstable.
At best, it could be an intro saying "this is what they're trying to do"; but you can also cover that in a blog post, right?
I was really unsure what the result would be -- I definitely shared your concerns when I started.
The core of Dart is surprisingly stable -- the team is doing a really solid job of not yanking the rug out from under developers' feet. Sure, I could have stopped at one blog post, but I ended up with 90 and still feel like I have more in me.
In the end, I was pleased with the result. But I might be biased :)
At best, it could be an intro saying "this is what they're trying to do"; but you can also cover that in a blog post, right?