[aardvark]

The copywriting is a little over the top, but my suggestion is for the book itself.

I'd like to see more details. Your sample chapter on Lexers, for example, would be much stronger if you went into more details (maybe 3-4 pages) on how a scanner identifies a token, how it knows when it has reached the end of a word, how it recognizes and handles whitespace, why it's important to keep track of indentation and newlines, what is the difference between keywords and other identifiers, etc. Maybe also give a written explanation describing what each section of your lexer for Awesome is doing.

Please consider this as constructive criticism: I think the book is a good idea, but I also think it needs more meat. I don't know how easy it is to revise it at this time, but I think you'd have better luck if you added more details.

[plinkplonk]

"The copywriting is a little over the top,"

a little?

"Become the next Guido Van Rossum, Matz, Larry Wall or Rasmus Lerdorf by creating your own revolutionary programming language in a few days"

Heh heh!

[netghost]

Lose 120 pounds in six minutes!

[geeko]

...even if you only weight 80 pounds.

[dkersten]

I've always wanted to weight -40 pounds; where do I sign up?

[macournoyer]

I sure do take this as constructive criticism :) The idea of the book is to build a simple language not the strongest or more complete one ever. I'll add more details and change the copy on the site. Thx a lot for the suggestions!