3 ms·
Suggesting that single threaded concurrency is the right way to do it when building tooling is completely asinine.
by chrismsimpson 3y ago
Suggesting that single threaded concurrency is the right way to do it when building tooling is completely asinine.
- IshKebab 3y agoHe isn't suggesting that. He's suggesting it is the right place to start, in the same way that we normally start writing sync code with a single thread.
- chrismsimpson 3y agoNope. Direct quote: > “..and when you need to utilize multiple CPU cores, you just spawn multiple processes that listen on the same socket. This is a much better way of structuring servers..”
- IshKebab 3y agoThat's not a contradiction. He's saying that later when you need multithreading you can add it. You generally don't start with it. Of course for some projects you know up front you'll need multithreading but the point is that that isn't the default position.
- chrismsimpson 3y agoYes it is. Spinning up another process is not multithreading, like, literally. It’s multiprocess. I never cease to be amazed with the complete lack of basic CS literacy from JS script kiddies.
- IshKebab 3y agoI was using "multithreading" as a shorthand for "making use of multiple CPU hardware threads".