undefined | Better HN

0 pointsdeadbabe2y ago0 comments

You must perform physics calculations on the backend if they are significant features that influence player positions.

Node also only works off a single core.

0 comments

Node of course can work on multiple cores, using worker threads [1]. You can even share large data efficiently using a SharedArrayBuffer.

[1]: https://nodejs.org/api/worker_threads.html

deadbabeOP2y ago

It isn’t trivial to just split up a game into múltiple worker threads and keep everything in sync. With Go, it’s much easier.

holografix2y ago

Can you expand on the low hanging fruit of splitting a game into multiple goroutines?

What lends itself well to this?

1 more reply

moffkalast2y ago

There is still considerable overhead turning things into buffers and back. Was there ever a good reason given as to why passing an object to a worker normally has to convert everything to string and back? It is just so completely idiotic.

johnwheeler2y ago

I see. That makes sense.

j / k navigate · click thread line to collapse