3 ms·
Makes sense. Better than Ruby I guess. It's still not really concurrency, it just handles being single threaded better. JS is strange because of all the optimi
by throwaway189262 6y ago
Makes sense. Better than Ruby I guess. It's still not really concurrency, it just handles being single threaded better.
JS is strange because of all the optimization. It's technically multi threaded with IO but in a way that you only control the "main thread". Reminds me of old UI work
- coldtea 6y ago>It's still not really concurrency Well, it also has Workers, which is.
- jiofih 6y agoConcurrency != parallelism. You can of course run a multi-process cluster, but that’s besides the point (and these days it’s best to run a single process inside orchestration like k8s). Basically almost every high performing server atm is running on some form of event loop / cooperative multi-tasking. Ruby Puma, Gunicorn, rust’s tokio and async/await, goroutines... Java is probably the big exception here (if you’re not using VertX et al) and we all know the pain of thread safety.
- throwaway189262 6y agoVery true. Go is an exception, and some day Java will be as well. They're both going route of userspace threads instead of reactive API's, thankfully.