>His suggestions were Erlang and Go which are arguably better approaches in a purely technical dimension to NodeJS. I would say that it is based on a subset of

>His suggestions were Erlang and Go which are arguably better approaches in a purely technical dimension to NodeJS. I would say that it is based on a subset of the technical dimension. Maybe Erlang and Go might have nicer ways to handle concurrency flows but if it doesn't have a library X to communicate with backend component Y then there is a technical reason not to use it.