4 ms·

I love the meta-ness of this comment. Not sure if it was intentional :-) One concrete example of naming a problem is “callback hell”. Example of “telling a sto

I love the meta-ness of this comment. Not sure if it was intentional :-) One concrete example of naming a problem is “callback hell”. Example of “telling a story” to explain it: https://tirania.org/blog/archive/2013/Aug-15.html https://tirania.org/blog/archive/2013/Aug-15.html Once you have a few articles like this, the quality of discussions on the topic rapidly goes up. For React, David Nolen’s and James Long’s early posts did the same thing.

munk-a 8y ago
It was, to my knowledge there isn't a great way to flag that sort of thing on the web (short of * WINK *)... I thought the fact that I apologized for having "overreacted" when discussing the blog post hosted on overreacted.io would be a bit of a give away. That callback hell story differs from the one above in that I think it delivers a much better summary statement at the end and way forward - I have some opinions on it's aim as I think it is eschewing power in terms of a more comfortable expression for imperative programmers - but the article is well sized, clear, humorous and suggests a solid remediation for the perceived problem.