3 ms·
I've no horse in this race, but the comment.. "I have written production level code in Erlang, namely a BitTorrent client good enough for everyday use" ...see
by allertonm 16y ago
I've no horse in this race, but the comment..
"I have written production level code in Erlang, namely a BitTorrent client good enough for everyday use"
...seems to be going some way towards proving the Acharya's point #4 for the following reasons:
1) No reference to any actual users of the code apart from the author himself.
2) No link to where the code is available.
3) Code is a single-user client, when Erlang's strength is usually considered to be in multi-user servers.
It's not obvious that the author understands what is meant by "production level", since the project mentioned does not even appear to meet the most liberal possible interpretation of this term, which would be "shipped".
- swannodette 16y agoetorrent, https://github.com/jlouis/etorrent https://github.com/jlouis/etorrent
- allertonm 16y agoThanks, that does improve jlouis case quite a bit. (And makes me sound a bit uncharitable too. Merry Xmas!)
- jlouis 16y agoToo add: BitTorrent is heavily "multi-user" in the sense that you communicate with numerous peers (200+ is not uncommon). Each peer gets turned into a small set of processes inside etorrent (4 per peer), so it quite heavily makes use of the process-parts of Erlang. I wouldn't say you need to have to be a "server" in the usual sense to argue the point. In the case of BitTorrent the client is also a server however.