4 ms·
Node didn’t introduce callbacks to JavaScript, they were present in the earliest browser APIs (img.onload, etc.)
by pavlov 2y ago
Node didn’t introduce callbacks to JavaScript, they were present in the earliest browser APIs (img.onload, etc.)
- Yoric 2y agoFair enough, I meant CPS-style programming.
- layer8 2y agoThese were just regular events on the UI thread, not any different from onclick etc., IINM.
- pavlov 2y agoSo, the same thing as callbacks in Node.
- fenomas 2y agoWhen people talk about a callback in this kind of context they usually mean one function passed as an argument to another, in order to be invoked with the latter function's return value. Not event handlers like onclick, etc.
- layer8 2y agoI’m not familiar with Node, but static event handlers aren’t usually referred to as callbacks in that context. “Callback” implies that something is being called, for it to call back to the client code. That’s not what’s happening with the onxxx event handlers. There is no “back” there. The event loop simply calls “forward” into the JavaScript code.
- pavlov 2y agoI don’t know what you mean by “forward” because there is no difference between these two: img.onload = function() {…} img.src = “some url” img.load(“some url”, function() {…}) The early JavaScript APIs use the first style, but the result is the same.