[ art / civ / cult / cyb / diy / drg / feels / layer / lit / λ / q / r / sci / sec / tech / w / zzz ] archive provided by lainchan.jp

lainchan archive - /λ/ - 17864

File: 1470795031590.png (12.92 KB, 300x127, erl.png)


Who Erlang/OTP here?


Had some fun with Elixir some month ago but I'm missing a type-system in Erlang.


I also got sucked in by Elixir a bit, though I found OTP to be the main selling point. Really a great way to do functional programming for networks with binary data.


Not the same but there's:


Which you can also use in Elixir and there's also TypeSpec for just Elixir.


I'm interested in learning Erlang, as my current language repertoire is lacking in concurrency.

I was going to familiarize myself with LFE, but I feel that I should also make myself familiar with normal Erlang.

I understand that I can search all of this, but I want to help jumpstart some Erlang discussion.

Is Erlang a standardized language? If so, where can I find the standard document?
Is the syntax of Erlang complex? Please note I come from languages such as Lisp and Forth.
I would ask if Erlang will change how I think about programming, but I imagine the focus on concurrency will certainly do so. I've not yet used a language in which concurrency is anything but a convenience or optimization, rather than a fundamental language feature.
It's my understanding that Erlang is focused around concurrency and error recovery. How does the error recovery in Erlang compare to Common Lisp? Common Lisp divides error recovery into signalling more general conditions, establishing recovery code, and handling conditions optionally with the recovery code.


File: 1482154670222.png (368.6 KB, 200x134, erlang otp2.png)

>tfw Joe Armstrongs book will probably get delivered today
I might try to ressurect this thread with some type of project in the summer, I was thinking of building a IRC-server with OTP


Elixir is so much better a language than Erlang. At some point callbacks are going to reach their limit as to what they can do with concurrency and Elixir will be the main backend language everyone uses. Because the syntax is so Ruby-like it will be easy for backend web programmers to transition.


I love this image. Is there an erlang otp1.png? Thanks, that Erlang video (and jokes of it) are my favorite. I should dig into Erlang deeper though.


The Erlang motto is: "Let it Crash". Erlang is designed to handle networks of millions of processes distributed over thousands of servers. When something goes wrong it telephony it doesnt make sense to stop everything to try and fix it. Processes in Erlang syntactically appear to be like functions that send and accept messages. The processes are handled on large scale by the OTP which is like an operating system scheduler that also supports manager processes that watch over worker processes. You can build large hierarchies of manager/worker processes with the OTP


Joe Armstrong recently interviewed Alan Kay the inventor of Smalltalk. Anyone who knows about Alan Kay knows he hates the association of Smalltalk with objects and always meant for it to be based on message passing without any dependence on shared state. Alan Kay turned out to be quite an asshole and completely ignored Joe Armstrong's presences so it was basically him talking to the audience the whole time. Still important points were brought up about the future potential of programming.


Nah, the erlang otp1.png is just the same image in lower quality that I found first


Tried out Elixir with Phoenix earlier this year. I really like Erlang's message parsing.