Errata checkpoint - chapter numbers changed

21 views
Skip to first unread message

Thomas Shinnick

unread,
Aug 21, 2015, 5:42:22 PM8/21/15
to Exploring ES6
Would you consider adding a note to the web page linking to the errata spreadsheet and into the spreadsheet that a new chapter - 4 - has been inserted which has incremented all later chapter numbers by one?  This impacts people trying to scan the errata to avoid duplications and/or check if the text has a bug or they're just misunderstanding.

The first new erratum after the chapter number changes looks to be
    8.8.2  Parsing JSON via JSON.parse()

Adding a note into the spreadsheet before that line, that chapters 4-28 are now 5-29 would solve some mysteries.

(also the mystery of whether errata will be noticed - there's 69 or so currently)

Axel Rauschmayer

unread,
Aug 21, 2015, 6:22:30 PM8/21/15
to Exploring ES6
Would you consider adding a note to the web page linking to the errata spreadsheet and into the spreadsheet that a new chapter - 4 - has been inserted which has incremented all later chapter numbers by one?

Right, thanks for this feedback, I’ll find a way to fix this!


(also the mystery of whether errata will be noticed - there's 69 or so currently)

Classy – sarcasm! I’m not sure you appreciate how much work it is to write a book with over 500 pages. I have always clearly stated that the book is work in progress – there are still whole chapters missing, which I’m currently busy writing. The errata will be fixed eventually.

Thomas Shinnick

unread,
Aug 21, 2015, 10:13:13 PM8/21/15
to Exploring ES6
On Friday, August 21, 2015 at 5:22:30 PM UTC-5, Axel Rauschmayer wrote:
Classy – sarcasm! I’m not sure you appreciate how much work it is to write a book with over 500 pages. I have always clearly stated that the book is work in progress – there are still whole chapters missing, which I’m currently busy writing. The errata will be fixed eventually.

I can't imagine how much work.  (I obsess so over minor details I could never make such progress.)  And indeed you are trying to tie together as a coherent whole, the disparate things which were the individual successes collected together and named 'ES6'.

Pausing/backtracking to deal with minor errata is jarring and a bit disruptive.  But it *does* inspire the masses!  (the many eyeballs theory) :-)

Axel Rauschmayer

unread,
Aug 24, 2015, 7:01:06 AM8/24/15
to Exploring ES6
I have updated the section headings.


Pausing/backtracking to deal with minor errata is jarring and a bit disruptive.  But it *does* inspire the masses!  (the many eyeballs theory) :-)

True. I’ll move the errata up in my to-do list. I just didn’t like the insinuation that I didn’t care.
Reply all
Reply to author
Forward
0 new messages