Live data from Hacker News

Lisp Flavoured Erlang 1.0 released after 8 years of development

github.com

51–60 of 96 posts

Re: Lisp Flavoured Erlang 1.0 released after 8 years of development

#51
post #17

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

rvirding was also one of the creators of Erlang itself at Ericsson.

Re: Lisp Flavoured Erlang 1.0 released after 8 years of development

#52
This looks really interesting. I installed it easily through Brew. REPL seems to work fast.

Now if my Clojure flawored Lisp starter level knowledge could be somehow transformed into Erlang flawor...

I wrote this:

    > (map (lists:seq 1 10) (lambda (a) (io:format a)))
and this happened:

    #M((1 2 3 4 5 6 7 8 9 10) #Fun)
So, I'm not quite there yet. Hopefully somebody can make a Clojure to LFE comparison.

And using Elixir based things like Phoenix springs to mind...

Re: Lisp Flavoured Erlang 1.0 released after 8 years of development

#53

This looks really interesting. I installed it easily through Brew. REPL seems to work fast. Now if my Clojure flawored Lisp starter level knowledge could be somehow transformed into Erlang flawor... I wrote this: > (map (lists:seq 1 10) (lambda (a) (io:format a))) and this happened: #M((1 2 3 4 5 6 7 8 9 10) #Fun ) So, I'm not quite there yet. Hopefully somebody can make a Clojure to LFE comparison. And using Elixir…

Map is a constructor in this case. You'll want lists:map/2 (fn comes first). I don't know LFE much so there may be sugar of sorts for this, perhaps a comprehension syntax.

Re: Lisp Flavoured Erlang 1.0 released after 8 years of development

#54
post #17

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

Shame about luerl not supporting __metatable properly. That's half of why Lua is awesome.

Still a massive achievement, awesome stuff.

Re: Lisp Flavoured Erlang 1.0 released after 8 years of development

#55
post #44

Earlier quoted context omitted.

Readable stack traces. Unfortunately, the JVM is the culprit here. I like Clojure's syntax, and some other bits, but if I were to chose a Lisp that runs under another system like Clojure, I'd choose Shen [1]. [1] http://shenlanguage.org/

>The Shen kernel is under BSD and currently runs under CLisp, SBCL, Clojure, Scheme, Ruby, Python, the JVM, Haskell and Javascript. Hm, I guess I can't imagine how that would work, one language running under all those environments?

Shen is built on it's own simplified parent dialect that is easily implementable in pretty much any language. Once you implement that core, everything else comes along for free, in theory.

Re: Lisp Flavoured Erlang 1.0 released after 8 years of development

#56
post #39

Earlier quoted context omitted.

This is a feature to me more like a limitation. I do not like optional arguments &rest style. In Erlang you need to have explicit number of arguments and need to explicitly implement them. I really like that. Keep in mind that default values are trivial to implement when the smaller arity function calls the higher arity one with added values. Or you can call in yourself to the higher arity function and specify the pa…

In Erlang you need to have explicit number of arguments and need to explicitly implement them. Or, you know, just use lists as parameters. That's the standard Erlang pattern for unknown parameters lengths (e.g. io:format("debug ~s because ~p~n", [SomeString, SomeType]))

I think io:format has fixed number of arguments(2), the text that you use as a template and the second parameter is a list of things that you will be using in the template.

Re: Lisp Flavoured Erlang 1.0 released after 8 years of development

#59
post #38

Elixir is really not similar to Ruby and the comparison wears thin. Wasn't Elixir just created because 100%-Ruby-til-Death programmers refuse to learn any other non-ruby-like syntax? It's like their brains would shatter into a brillion pieces if they ever had to think about tail recursion. have made the developer experience second to none Except, LFE isn't a giant community and companies and organizations and confere…

> It's like their brains would shatter into a brillion pieces if they ever had to think about tail recursion.

Come on, man. Your anti-Rubyist bias is showing way too clearly. I switched to Elixir from Ruby (or rather, am still trying to move all my project work over), and I grokked tail recursion just fine.

> LFE is a nice project that grows as people use it without trying to form an army/cult around it like so many other languages do these days

No product (language or otherwise; trying to include Apple, here) ever "tried to form a cult around itself." That is just a natural happening when a new thing is really really cool. So discounting something because of its popularity is sort of an "argumentum ad populum" fallacy in reverse (arguing for OR against something because of its popularity).

Re: Lisp Flavoured Erlang 1.0 released after 8 years of development

#60
post #16
post #10

Earlier quoted context omitted.

It started in 2007 with the release of Clojure and there are still plenty of paren keys around.

The Lisp renaissance started in December 1999 with SBCL being forked from CMUCL.

Agreed. Well, with the date, anyway ;-) (though I am an SBCL user) Somewhere around 2000 we saw the end of AI winter. This most likely owes something to the fairly impressive Lisp marketing that PG did. Within a few years, several new Lisp books came out, and a few years after that we saw what the other poster mentioned: but not Just Clojure, a plethora of Lisps. To mention just a few: Clojure, Liskell, and LFE (LFE was actually started in 2007, first released in 2008). To the best of my knowledge all of these were completely unknown to each other at the time of their inception, and thus indicative of probable momentum in the wider Lisp community from an earlier time, possibly the once-again-growing acceptance of Lisp that started ~2000.
Post reply on HN