rvirding

13 ms·

31.
by rvirding 11y ago
The OTP are identical because both use the same OTP, the original Erlang OTP. Elixir just puts a wrapper around it to give a more elixir feel. And add default callbacks which I personally don't like.
32.
by rvirding 11y ago
One difference is that Erlang's concurrency and error handling in the language is more basic than Akka's and does not directly provide fault-tolerance through supervision but does provide the primitives to implement. All of OTP is
33.
by rvirding 11y ago
That is a very good paper, well worth reading!
34.
by rvirding 11y ago
I was going to make a nasty comment and refer to Schiller, but I won't. The jokes on you. :-)
35.
by rvirding 11y ago
Who got it from elsewhere. ;-) The sequential part of Erlang is basically a simple functional language with nothing really unique, except maybe for binaries. It is the concurrency and error handling where the really good bits are.
36.
by rvirding 11y ago
Just want to point out that atoms and function names ARE the same in that function names are atoms, they must be in fact as that what the system demands. So are module names for that matter. That is why if you want a function with a "f
37.
by rvirding 11y ago
It was originally in the original Erlang interpreter written in Prolog but you could use it for back-doors in the communication so we removed them. If you sent an unbound variable in a message then the receiving process could reply by bindi
38.
by rvirding 11y ago
They got that from Erlang :-)
39.
by rvirding 11y ago
Well, you can filter, map and fold over maps so there is not really much missing. And they are efficient both when they are small and large.
40.
by rvirding 11y ago
I thought they all must be java.
41.
by rvirding 11y ago
If you seriously look at the Erlang syntax you will find it is very simple, concise and consistent. We wanted to keep it simple. Yes, it different from most OO languages, most functional languages look different, but that is not surprising
42.
by rvirding 11y ago
It is actually being used in products.
43.
by rvirding 11y ago
The name was the hard bit, elua was already taken, erlua sounds funny and erlanglua is so long. So it became luerl.
44.
by rvirding 11y ago
Yes, I am a language nut :-) and I like to implement languages. It is a very complete Lua implementation in that it supports all of Lua 5.2 except for coroutines and many of the standard libraries. There is of course a good erlang interface
45.
by rvirding 11y ago
Of course metatables are supported, it wouldn't be much of a Lua without them. Luerl is standard Lua 5.2 except for coroutines.
46.
by rvirding 11y ago
I know I missed this but I do want to make some (general) comments: - Erlang, the language and system, was designed for highly concurrent and fault tolerant systems. In many ways these were more important than raw throughput in that if it c
47.
by rvirding 11y ago
Yes, but the VM clock guaranteed more, every time you access the clock using erlang:now() you would get a monotonically increasing value. Practical to be sure, but not scalable.
48.
by rvirding 11y ago
Why not just write it in hexadecimal?
49.
by rvirding 11y ago
Aaaahhhh, the syntax is different! Help, help, the world is coming to an end.
50.
by rvirding 11y ago
If you replace "Joxa" with "LFE" here you would get a good description of LFE.
51.
by rvirding 11y ago
Not quite, LFE is a self-contained Lisp system with all the things you would expect a lisp system to have. It has been designed to run on the Erlang/OTP system and to efficiently use all the features of that system and its VM. This mea
52.
Lessons from Erlang VM [video](youtube.com)
68 points by rvirding 11y ago|6 comments
53.
by rvirding 11y ago
They don't handle errors very well.
54.
by rvirding 11y ago
Why am I getting this strong deja vu feeling? Hmm. Oh, now I know! These were exactly the type of problems we were attacking, and solving, 25 years ago when we were creating Erlang. How you build concurrent, fault-tolerant and non-blocking
55.
by rvirding 12y ago
The best thing that we weren't faking this. We did actually run though the whole sequence as was shown in the movie with having a call going while another part of the crashed and was fixed.
56.
by rvirding 12y ago
I found that being a Lisp-1 made it inconsistent so I went with Lisp-2. Why should I be able to multiple functions with the same name but different no of args at the top-level (which you can and is commonly used) but not in local functions?
57.
by rvirding 12y ago
Yes, implementing languages is fun, implementing lisp doubly so.
58.
by rvirding 12y ago
Being an erlang programmer I am so used to programming for the correct case and not to check errors but let the process crash when you get an error or, rarely, use a try that I find this style of programming completely wrong. It is what we
59.
by rvirding 12y ago
You can use similar methods for interfacing C as well, if this is a better way for you to interface fortran.
60.
by rvirding 12y ago
The heading does actually say for which language this is: elixir.

More ›