@pavlobaron @b_erb I understand the reasons, but that doesn't make it less strange that almost no one chose the asynchronous path

@pavlobaron @b_erb And here I thought they formed the basis for Erlang's I/O too

@pavlobaron My expectation was/is that on Beam, you need as many Erlang processes as parallel connections, but not as many threads

@pavlobaron I was just puzzled by your negative attitude to select/poll :-)

@pavlobaron I see; I was lumping select/poll/epoll/kqueue and all the others together. The real anti pattern is one thread per connection

@pavlobaron what book did you send him? interesting :D