Post

The goal instead is to focus on how the various parts of the JavaScript language itself work, why they are defined the way they are, what those decisions mean for performance and complexity, etc. It's not intended to teach how to use the language but why it does the things it does...

... and honestly, it's probably the most difficult thing I've worked on in a long time. It's fairly easy to say, "Follow steps A, B, and C"... it's a whole lot more difficult to explain why those are the steps and to explain what's happening when those steps are taken! ...

... The difficulty really lies in knowing what exactly to talk about, knowing how to frame it so that it is approachable to new and intermediate developers, and knowing how to discuss it so that the critical points come through without getting lost in the weeds... but why are these details needed?

how much will you talk about streams/buffer? There's async iterator/generator which seems to be what some Node core members are pushing, but some Node APIs warn that the iterators are slower compared to using callbacks. ANd I'd love to see how to use any stream API for high-performance usecase.