3 ms·

not to be overly pendantic but events and messages mean pretty different things and have different applications. Same thing with queues and buses. I suspect th

not to be overly pendantic but events and messages mean pretty different things and have different applications. Same thing with queues and buses. I suspect the author knows more about this than me but plays a little fast and loose in their explanations. I feel it's important to have disipline in our vocabulary so that people learning the material can participate in more advanced discussions as they grow. That said, I really appreciate the overall content and using the context of games for broadly applicable concepts is a great way to promote them (and funny as generally commercial games have some of the loosest "structure" of any code I've seen).

mindcrime 6y ago
not to be overly pendantic but events and messages mean pretty different things and have different applications. Same thing with queues and buses. I agree with what you say. But I'd add the suggestion that this depends on the context to some extent. For example, in the world of hardware and electrical circuits, a "bus" and a "queue" have almost no connection at all. But in the world of enterprise software, an "enterprise service bus" is often thought of as basically "a bunch of queues and a message router". Of course that's imprecise as well, since it ignores orchestration... which just goes to show even more how fuzzy some of these terms are in practice. I feel it's important to have disipline in our vocabulary so that people learning the material can participate in more advanced discussions as they grow. I generally agree, but I think this may be a case where "that ship has sailed." :-(