News for hackers. Stuff that matters.
Re:Erlang vs node.js by davidw on Thursday April 29, 2010 @11:16AM (#1304703)
Part of my point in the article is that, while node.js is not as good as Erlang, it may be "good enough" for a great many web/network things where Erlang might be considered for its strengths. It's sort of a 'disruptive innovation' situation.
Re:Erlang vs node.js by jerf on Thursday April 29, 2010 @11:28AM (#1304746)
And that's fine. I rather expect you're totally correct in terms of describing what's going to actually happen; Erlang is a non-Algol language and while that's slowly becoming more respectable we've got a long ways to go before it is considered as anything but a negative by the vast bulk of programmers.

It's just that I've actually been down this path a few times with other apps and I feel a responsibility to raise a flag and point out that all applications tend to grow and building with a base that will cause your code to explode in complexity as you tend to grow is not the best plan, but I also know that this is very firmly in the class of things people have to learn for themselves. And the cute little proxies and such aren't bad, it's surprisingly hard to guarantee your app stays in the class of "cute little".

One of my other work apps is actually something built on the Perl wrapper around glib, using its event library, because I ended up having no choice for other reasons (was wrapping a C library and local political concerns wrote Erlang out). And ye gods, the mess, the mess, and the bugs, the bugs. Event chains four or five layers deep in callbacks (multistage login processes being wrapped by other multistage login processes, oi). It's the same exact organizational pattern as Node.js, and it just doesn't scale, even when you know what you're doing. Every trick I know brought to bear to simplify and improve (plugins, simulated generators with goto at a couple points, equivalents to the func chaining hack linked above), but you just can't overcome the weakness of the primitives.

Re:Erlang vs node.js by akkartik on Thursday April 29, 2010 @06:10PM (#1306249)
I read your comments on node.js with interest, but I object to being called an 'algol-like' programmer just because I can't deal with erlang.

I work with haskell and lisp just fine, and I can find my way around monads, closures and continuations. It's just the prolog syntax I can't get past.

That and a million little niggles. How do you quit from erl, anyway? Is there a faster way than C-g C-c a? [update: argh, C-\ has thwarted me for years. http://www.erlang.org/faq/getting_started.html It's hard to describe why - it's always obvious in hindsight - but erlang has been extremely painful to learn. I have no trouble with documentation and man pages, but with erlang it seems there's always one more place to check.]

I can't wait for lfe to mature.

Re:Erlang vs node.js by jerf on Wednesday May 05, 2010 @01:44PM (#1321877)
Sorry, I only saw this much later. When I say that Erlang is non-Algol, it is not a criticism of a given programmer. It is a criticism of the industry as a whole, that nothing that looks like Algol can succeed anytime soon.

Erlang is full of frustrating quirks and in other contexts you can find me complaining about them and how they don't all go away when you get used to them. (; , . is just plain BS.)