2 ms·
Cause Erlang is a point solution that is totally painful outside of its target domain and has practically no library support.
by dalice 18y ago
Cause Erlang is a point solution that is totally painful outside of its target domain and has practically no library support.
- yariv 18y agoYou can call Java (or Python, Ruby, C etc) libraries from Erlang if you really have to. I'd bet Erlang's libraries would be quite sufficient for a wide range of apps, though. Where did you run into pain trying to use Erlang outside of telcom apps? Just curious...
- mikkom 18y agoAlso remember where java started (oak) - a much more point solution than what erlang has ever been.
- astrec 18y agoYa know, when I first this comment on library support I thought "Well kinda..." but after a couple of hours mulling it over not so much. Erlang has a pretty good set of standard libraries, and whatever missing is relatively easy to build yourself, by comparison. Granted, there are some very good OS Java libraries, but there's also an awful lot of drivel - one need only fire up their profiler to verify it. I'd say you're being quite uncharitable to Erlang.