Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

He 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.


Nope. 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..”


That'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.


Yes 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.


I was using "multithreading" as a shorthand for "making use of multiple CPU hardware threads".




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: