> Threads are just kind of hard to use with gc:refc, that is why gc:arc is > getting worked on.
I'm still confused as to which GC is the default. I thought it was ARC, but what I'm reading recently makes it sound like ARC isn't quite stable enough yet. > Just regular threads are probably better if you are just writing and reading > from a single websocket connection. Async and threads are orthogonal, not opposite choices. What interests me about async/await is how it cleans up the control flow in source code, avoiding "callback hell". Again, I'm considering porting a large existing project, not writing something from scratch. I already know the requirements and the architecture. Nim is different from C++ but that doesn't mean I'm going to change the design to single-threaded. I definitely need multiple threads because the WebSocket messages invoke tasks that may be CPU-intensive or just block a while (database calls.)
