First of all, don't start a flaming debate of what I write here. Nobody likes that in their inbox. See this a my comments to the authors and If you disagree, I'll promise to be stupid here on my own....
When reading a book about any topic the What, Why and How questions must be approached by the writers to orientate the read, that's basics. Most of us Rotor-geeks skip the What and Why since it's the How that give us the thrills. However, being a How-guy I occationally meet disorientated people in the real world and than the Why question pops up, like "why spending time on Rotor when it's the commecrial product you should focus on?" Cutting to it, I would have liked a little more elaboration around the Why than the 2 sentences under paragraph "A CLI Implementation in Shared Source Rotot" (ch 1 ~p.13). There you start of promising with the words "In particular, the SSCLI had three goals to meet...". I still will buy the book and devote time to Rotor, but I would have liked to read the authors oppinion on why I should and perhaps give me another approach on the Why question. Let loose and share you oppinion! When will you write a book about Rotor again? Cheers Christer
