21–30 of 96 posts
Just waiting for the day when someone launches a js version then the whole world is gonna be coding on erlang vm I think.
I doubt it. IMO Erlang is fundamentally a different model of programming than JS and what about mutability and things such as pattern matching? It quickly becomes apparent that it would not be much like JS if it was to take advantage of all of Erlang's best bits.
Just waiting for the day when someone launches a js version then the whole world is gonna be coding on erlang vm I think.
I doubt it. IMO Erlang is fundamentally a different model of programming than JS and what about mutability and things such as pattern matching? It quickly becomes apparent that it would not be much like JS if it was to take advantage of all of Erlang's best bits.
> A proper Lisp-2, based on the features and limitations of the Erlang VM What are limitations?
One obvious example is that AFAIK the VM doesn't support functions with a variable number of arguments (foo/1 and foo/2 are two separate functions). This means that you can't have CL-style &rest or &key arguments.
Great news! I wanted to learn BEAM/OTP, but had tried Erlang briefly years ago, and then went back to Common Lisp. Now I can try to learn BEAM/OTP in a syntax that is more appealing to me than Elixir's Ruby-like syntax. I like Elixir, and it is very popular, but true runtime macros are available in LFE 1.0. In addition, Robert Virding was one of the co-creators of Erlang, so his devotion to bringing the best Lisp he…
Elixir really is a brilliant language and José et al have made the developer experience second to none with hex, mix, the language guide and docs. Compare how you bring up a repl: Elixir, type iex; LFE, cd into LFE dir, type ./bin/lfe. (EDIT: this is incorrect, see child) Trivial example and something easily fixed if it bothers you, but it's emblematic of the attention to detail that has gone into devx. I am deeply in love with Elixir. That Robert co-authored Erlang should not mean giving Elixir any less consideration IMO.
That said I sincerely wish to congratulate Robert on this 1.0, I look forward to using LFE in anger for something very soon now it is 1.0 (and it will be easy to slip in an LFE module into one of my OTP apps). Exciting times for the Erlang ecosystem.
I've stumbled into an interesting related comment on twitter, didn't know: "#Erlang based language ecosystem is more diverse than many know: #efene #reia #lfe #luaerl #erlog #elixir #mercury" https://twitter.com/BillBarnhill/status/670601359016771584 edit: Wow, and many of them seem to actually be by the same rvirding who authored lfe: https://github.com/rvirding/luerl https://github.com/rvirding/erlog
My exposure to the Erlang world is limited to having read the first few chapters of Programming Elixir. Is interop trivial? Can you easily use Erlang, Elixir, and LFE in the same project?
Yes, compiling a module where the source was written in another language is no different from calling a module written in the same one. In Elixir any time you call a module that starts with a `:` it has most likely been written in Erlang.
Great news! I wanted to learn BEAM/OTP, but had tried Erlang briefly years ago, and then went back to Common Lisp. Now I can try to learn BEAM/OTP in a syntax that is more appealing to me than Elixir's Ruby-like syntax. I like Elixir, and it is very popular, but true runtime macros are available in LFE 1.0. In addition, Robert Virding was one of the co-creators of Erlang, so his devotion to bringing the best Lisp he…
Elixir is really not similar to Ruby and the comparison wears thin. This is my opinion after having used Elixir daily for the last 1.5 years and Ruby for 10 years before that. Elixir really is a brilliant language and José et al have made the developer experience second to none with hex, mix, the language guide and docs. Compare how you bring up a repl: Elixir, type iex; LFE, cd into LFE dir, type ./bin/lfe. (EDIT: t…
Is that a joke?
> If you have installed LFE, then you may start the REPL from any location:
$ lfe
[0] because you may not want a system-wide LFE and LFE is being a nice citizen in explicitly supporting that use case.
Earlier quoted context omitted.
Elixir is really not similar to Ruby and the comparison wears thin. This is my opinion after having used Elixir daily for the last 1.5 years and Ruby for 10 years before that. Elixir really is a brilliant language and José et al have made the developer experience second to none with hex, mix, the language guide and docs. Compare how you bring up a repl: Elixir, type iex; LFE, cd into LFE dir, type ./bin/lfe. (EDIT: t…
> Compare how you bring up a repl: Elixir, type iex; LFE, cd into LFE dir, type ./bin/lfe. Is that a joke? > If you have installed LFE, then you may start the REPL from any location: $ lfe what you quoted is if you're running LFE straight from the git clone[0], and noted so. [0] because you may not want a system-wide LFE and LFE is being a nice citizen in explicitly supporting that use case.
> A proper Lisp-2, based on the features and limitations of the Erlang VM What are limitations?
One obvious example is that AFAIK the VM doesn't support functions with a variable number of arguments (foo/1 and foo/2 are two separate functions). This means that you can't have CL-style &rest or &key arguments.
But surely one could call a function with one argument, which is a variable-length list of arguments, right?
Earlier quoted context omitted.
Elixir is really not similar to Ruby and the comparison wears thin. This is my opinion after having used Elixir daily for the last 1.5 years and Ruby for 10 years before that. Elixir really is a brilliant language and José et al have made the developer experience second to none with hex, mix, the language guide and docs. Compare how you bring up a repl: Elixir, type iex; LFE, cd into LFE dir, type ./bin/lfe. (EDIT: t…
> Compare how you bring up a repl: Elixir, type iex; LFE, cd into LFE dir, type ./bin/lfe. Is that a joke? > If you have installed LFE, then you may start the REPL from any location: $ lfe what you quoted is if you're running LFE straight from the git clone[0], and noted so. [0] because you may not want a system-wide LFE and LFE is being a nice citizen in explicitly supporting that use case.
$ brew install erlang
$ git clone ...lfe.git
$ cd lfe; make && make install
$ lfe