Chapter in question: https://github.com/getify/You-Dont-Know-JS/blob/master/es6%20%26%20beyond/ch2.md#template-literals

The suggestion seems to be that the template literals would be all about strings; there's only examples that result in strings, and phrases like "final string value" and "generating the string from the literal" are used in what should be a general context, but the tag function

• Dynamic variable naming.
• Internal variables.
• Turn the non-functions into functions.
  • This is so tests can be written.
  • It also shows a working use case for the task.
• Add a CONTRIBUTING.md.
• Look into side effects of using shopt and set.
• /dev/tcp
• Convert to pdf
  • Add a cover.
  • Add references.
• Write some

When using Firefox Mobile Browser and Firefox Focus Browser, and Chome Mobile Browser on Android 8.1.0, page visitors to https://docs.python-guide.org/ are shown the bottom of the page being viewed and must scroll to the top to read as one would normally.

Not sure what is causing the jump to the bottom of the pages but it seems pervasive throughout the site.

explanation behind that says it's just coercion of one type plus another.
What is happening there is actually a code block and a unary + which coerces the array into 0.
({} + []) would get the same as ([] + {}) understandably.

I think you make a very solid point in that section when you say that:

I do think you should be careful about the flow control part of return creating more implicitness in your function definitions. Try to figure out the most explicit way to express the logic; that will often be the best way.

But in your example I feel you do just the opposite. You add an extra variable that I need to keep t

it would be great to code along with your tutorial and finish it to have a full understanding of how to write OS.

But if i start it now, i will progress as much as the tutorial allows me.

when do u plan to finish your cool tutorial?

It would be helpful (especially for non techie folk) if the entry point for the book was more obvious.

Only because I read the Mastering Bitcoin book did I know to enter at book.asciidoc

Needs something like this: https://github.com/bitcoinbook/bitcoinbook/blob/develop/README.md#reading-this-book

Right now it's just a collection of links (the basic format of each entry is 'name - author'). It might be helpful to make room for 1-2 sentence explanations of the link, particularly as the list grows.

(PS this project is linked prominently from the website now)

I suggest changing listing 15-20 to a match block to make it look more rustean: https://github.com/rust-lang/book/blob/master/src/ch15-05-interior-mutability.md

I also wrote about this on the slack channel.
https://rust-lang.slack.com/archives/C1NCDGD47/p1566370266316700

I am happy to make this change if you believe it will be approved.