You forget that these examples are for beginners/junior developers. Double fat arrows in particular are hard to read for them, and quite frankly, shouldn’t even be in production code, especially not with a comment that ALSO has two fat arrows but with a completely different meaning. This is just bad for the casual code reader. (I know you explained this somewhere in your blog post, but shouldn’t code be self-explanatory?)
‘o’ is not a good var name either for an example.
Additionally, you introduce a notation you developed yourself, which is completely irrelevant to the closure problem and just used so you can comfortably write code that YOU understand — but why should OTHER people who read your post also be required to learn that other thing you did just because it is convenient to you? Keep it simple. While your points are all good and valid, you really need to improve in the way you try to convey simple bits of information to people who are actually willing to listen and learn from you — without forcing more of your perspective and work onto them than is necessary to explain the core problems and solutions you write about.