@Jared_Cave thanks a lot for this Jared! I think your feedback here echoes what a lot of people go through when they learn programming — I certainly don’t think it is just your own.
The problem here is one of balance — the language is designed as a complete system, and all the features are designed to be used together. When you only show a single feature, it can’t be made to do anything partularly useful, so you end up with trivial examples that don’t really demonstrate real world usage and therefore aren’t very memorable.
When you use multiple features together, the examples are less trivial and more memorable, but you are stuck with having to learn about multiple concepts at once.
When I have opted to do this in my course, I have tried to make the learning as non-jarring as possible, but I wonder how I can make it even less so? For example, I could include a box somewhere near the top in such cases where I explain what other JS features are used in this article, make it clear what is the central focus is, and reassure people that they don’t need to understand the other stuff right now, it is just there to help with the understanding of the central focus. I could also provide links to a bit more information, or just in-page info about the non-central features.
What do you think about this?