3 ms·
The point is, extending JS to support such constructs without requiring callbacks would be worthwhile, IMO [1]. However, making it obvious with a better API wou
by tomp 13y ago
The point is, extending JS to support such constructs without requiring callbacks would be worthwhile, IMO [1]. However, making it obvious with a better API would be necessary.
[1] Note, however, that it would turn JS's threading model completely on its head. Right now, the philosophy of JS is "single-process" threading model, with WebWorkers supporting a "multi-processing" concurrency model by isolating different threads of control. Allowing futures without callbacks would bring JS closer to Golang's concurrency model.