3 ms·

Isn't this just a good argument for event-based programming ala Twisted or Node.js, to avoid the system thread overheads altogether? It seems to me that progra

by cpr 17y ago

Isn't this just a good argument for event-based programming ala Twisted or Node.js, to avoid the system thread overheads altogether? It seems to me that programming with event-based frameworks like Node.js is much less fraught with peril, confusion, and error. (Having written a couple of small but complete (bare iron) real-time, thread/process-based operating systems (and applications for them) for workstation-class CPUs back in the 80's, I'm highly aware of the peril and confusion possible. ;-)

mcav 17y ago
That only works for one thread. Many (most?) cases for using multithreading are when you need to do something CPU-bound, for which event-based mechanisms don't help.
- cpr 17y ago
  In that case you can use webworker-like computational threads, avoiding global data locking, etc.