>>1 It would be most appreciated.
I guess you don't know any better. Hopefully wiser heads prevail here.
Name:
Anonymous2009-05-01 16:26
Thinking in Sepples is a very boring book. I tried to get into it during a long train ride, but it's just so mundane, so linear, plain, unexciting. I grabbed Thinking Forth instead, read it for two hours (happily and excitingly), then tried to go back to thinking in Sepples, but it didn't work. In other programming books, if there's abstract bullshite, it's there for a reason, and its high-quality bullshite that provokes thoughts. The only thing that the pseudo-abstract bullshite in TICPP2ed provoked was my annoyance at not getting to the point already.
Also, examples. When I get into something new, I want (semi-)real-life examples, like a JSON module or LISP, not a [b][i]FUQIN LIGHTBULB/i][/b]. So when I flip the pages, I think ``oh my, I wonder how would you exactly expand the cond to a chain of ifs'' and not ``why my light no work''.
ALSO, stop trying to be hip, Bjarne.
It's just a boring read, that's all.
This thread is ironic, because the best way of learning Sepples would without a doubt not be by reading a book about it. My bet would be that learning Se or Haskell would be the best way to learn Sepples.