erlang

I recently started looking into the erlang language. It is a functional language somewhat like lisp, but concurrency is built into the language in a very fundamental way. Has anyone out there worked with erlang before? Any opinions on the language?

It confused me. I wasn't sure how to write anything useful in it. If you become suitably enlightened, post with advice.

From what I have seen, erlang would be rather useful for writing control systems. Each concurrently running function could represent portions of the system. As input comes in, each erlang process could communicate with other erlang processes to get something done. The IPC between erlang process seems very easy. If your system ever needed to do a low level operation, you can always call external executable programs using the following:

os:cmd("program and arguments here").

Lastly, if you ever deployed a system using erlang, you can field upgrade it with 0% down time. You insert the new code into the running system, and it switches to the new code live.

erlang looks like a powerful tool. However, I am more used to designs using languages like C and Java. I bet it takes a different mind set to design a system using a functional language.

I recently started looking into the Java language. It is an enterprise language somewhat like C++, but failure is built into the language in a very fundamental way. Has anyone out there worked with Java before? Any opinions on the language?

I recently started looking into the Greek language. It is a moon language somewhat like Russian, but mathematical symbols are built into the language in a very fundamental way. Has anyone out there worked with Greek before? Any opinions on the language?

>>3
If your system ever needed to do a low level operation, you can always call external executable programs using the following:
os:cmd("program and arguments here").
LOL. How primitive and unEXPERTLY.

>>4 an enterprise language somewhat like C++, but failure is built into the language in a very fundamental way

I'm not sure I understand how it differs from C++.

>>5

lol what a joker

>>1
Erlang is awesome. I don't think I'd really consider using any other language for applications requiring significant concurrency or network features. The built-in fault tolerance is absolutely brilliant, especially when combined with Erlang's out-of-the-box distributed scaling functionality.

>>2
Advice: Read SICP. Functional languages are fun.

>>9
Erlang is awesome. I don't think I'd really consider using any other language for applications requiring significant concurrency or network features.
I wonder, do people like this ever actually program? Or do they just sit around, download the toy languages du jour, write Hello Worlds in them and fantasize about how cool it's going to be when somebody is finally going to use them? (Not counting Ericsson.)

>>10
Probably the latter. Obviously one can do great things with toy languages, but only a faggot would never consider using something else than the flavor of the week.

>>11
Well said.

>>10
There are people other than Ericsson that use erlang. Demonware use it in their game middleware stuff, for example.

>>10
I love using Haskell when I feel its appropriate (usually for esoteric problems and functional tomfoolery). And even though I use more practical languages for more practical tasks, learning Haskell has definitely improved my programming skills, so its not entirely useless.

If you look hard enough, there are some really awesome programs made from Haskell and Erlang.

>>14
Like the umpenteenth lambda calculus evaluator?

I wants lots and lots of some delectable pot!

Marijuana MUST be legalized.