4 ms·
> It's also not a very compelling argument for threading to say "web programs don't share a lot of state, so you don't have to worry about synchronization". Is
by sbov 16y ago
> It's also not a very compelling argument for threading to say "web programs don't share a lot of state, so you don't have to worry about synchronization".
Isn't this an issue with both models? Shared state is shared state, regardless of whether you use threads or an evented model. Unless you're only running on 1 CPU.
- tptacek 16y agoNo, because evented code (usually) is scheduled cooperatively; (most) conflicts are precluded. This goes out the window when you start forking processes and using shared memory, but at least then you're default-private instead of default-shared.