4 ms·

I'd love to debate the part about persistent call order but the rest of your comment has nothing to do with the content of my article and appears to be a generi

I'd love to debate the part about persistent call order but the rest of your comment has nothing to do with the content of my article and appears to be a generic rant. Could you help me see how it would result in "huge clusterfucks" with an example? Note React doesn't rely on particular call order. You can move your calls around any way you like. Just that it's persistent between re-renders.

RubenSandwich 8y ago
Dan, I've seen this a few times already. I believe people are misunderstanding "persistent call order" to mean that they cannot change call order between versions of their app. I wonder if another name would help people understand this, maybe: "Non-conditional call order."? That does better highlight that you are worried about conditionals. (It doesn't address the loop issuie though.) Hmm, here is another one. "Static call order"? I guess what I'm saying and what I'm reading from the parent comment is that they are misunderstanding the name.
- danabramov 8y ago
  Static is pretty good.