Readers discussing a classic 2015 article on function coloring argue that the concept extends beyond asynchronous programming to encompass exceptions, fallibility, and other paradigms. The discussion highlights that the primary friction caused by colored functions stems from a language's inability to abstract over different function types rather than the separation itself. Ultimately, commenters note that while the term has become an overused buzzword, resolving the underlying abstraction problem often requires implementing complex type system features like higher-kinded types.