top | item 29909389 Callbacks, Synchronous and Asynchronous (2011) 28 points| LiveTheDream | 4 years ago |blog.ometer.com 3 comments order hn newest klabb3|4 years ago Terminology opinion: I'm not too fond of the term callback for "synchronous callback" as described in the post. First, it doesn't actually "call back", and secondly why not just use "function"? bruce343434|4 years ago lambda, callback, function, closure, anonymous function, thunkIt's all pretty much the same.I like "synchronous callback" because this tells you two things:1. it's synchronous, no need to add memory barriers2. it _is_ a callback, it is called after the fact. load replies (1)
klabb3|4 years ago Terminology opinion: I'm not too fond of the term callback for "synchronous callback" as described in the post. First, it doesn't actually "call back", and secondly why not just use "function"? bruce343434|4 years ago lambda, callback, function, closure, anonymous function, thunkIt's all pretty much the same.I like "synchronous callback" because this tells you two things:1. it's synchronous, no need to add memory barriers2. it _is_ a callback, it is called after the fact. load replies (1)
bruce343434|4 years ago lambda, callback, function, closure, anonymous function, thunkIt's all pretty much the same.I like "synchronous callback" because this tells you two things:1. it's synchronous, no need to add memory barriers2. it _is_ a callback, it is called after the fact. load replies (1)
klabb3|4 years ago
bruce343434|4 years ago
It's all pretty much the same.
I like "synchronous callback" because this tells you two things:
1. it's synchronous, no need to add memory barriers
2. it _is_ a callback, it is called after the fact.