Yes, I'm aware of the concurrent mode contract. But do you see the Stockholm syndrome here? If I were to tell you that in order to use a hypothetical Floober f

Yes, I'm aware of the concurrent mode contract. But do you see the Stockholm syndrome here? If I were to tell you that in order to use a hypothetical Floober framework, your code must be tail call optimizable or else the framework has undefined behavior, surely you would think the author of Floober framework was insane. It seems strange, for example, to dismiss async functions on grounds of function coloring when the alternative is coloring functions with a conceptual requirement of "purity". Or to ignore the opportunity for a paradigm shift to something more naturally reactive (e.g. a la s.js) considering how there was already an API shift when going from OOP components to functional + hooks.