4 ms·
I think that comment I linked to was pretty good, actually and has some specific, actionable advice. Node.js feels like a Vespa that you can hop on and drive a
by davidw 12y ago
I think that comment I linked to was pretty good, actually and has some specific, actionable advice. Node.js feels like a Vespa that you can hop on and drive around. It's quick, it's agile, you could take a date on it and it'd be kind of fun, although once you have a family with kids it's not so useful. Erlang feels a bit more like a Boeing 747: you can certainly go far with it and do things the Vespa can't, but to even get in the cockpit you have to have a lot of training, and it might feel like overkill to do anything less than a big long trip.
Lowering those barriers to entry is important. Erlang will never be the easiest/quickest thing out there, but if it's a bit easier to get into it, it will, at the margin - meaning people who are undecided or on the fence - bring people in.
Package management is a big one.
Easy to get started examples is important too.
I think a more curious attitude would help some people too... thinking about why Erlang doesn't "sell well" rather than immediately placing the blame on others for not being "good enough" or whatever. The community is good, but there is some of "it's not a wart, it's a feature!" - perhaps more than elsewhere. I saw this in the Tcl world too, and it can be unproductive.
- wcummings 12y agoRebar and Erlang.mk are both very easy to use for dep management, and relx is exceptionally easy (one-line config to generate a simple release, which is portable & standalone)