by vdaniuk on 3/17/16, 2:04 AM with 91 comments
by eggy on 3/17/16, 4:40 AM
[1] http://extempore.moso.com.au/
by vdaniuk on 3/17/16, 2:07 AM
I feel that this LFE release further validates BEAM as a promising platform for future development of new programming languages. Also I look forward to reading SICP converted to LFE. Available chapters can be found here https://www.gitbook.com/book/lfe/sicp
by akavel on 3/17/16, 9:10 AM
"#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:
by rvirding on 3/17/16, 5:30 PM
* I am just going to ...
by Kuytu on 3/17/16, 7:30 AM
by jb1991 on 3/17/16, 8:31 AM
>LFE (Lisp Flavoured Erlang) has been designed to run efficiently on the Erlang VM and at the same time be a "real lisp" providing Lisp's good bits.
It also knocks Clojure a bit. What do you all think are the "good bits" of lisp that Clojure lacks?
by jarpineh on 3/17/16, 2:55 PM
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<lfe_eval.12.88887576>)
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...
by namelezz on 3/17/16, 4:38 AM
What are limitations?
by aidenn0 on 3/17/16, 4:27 PM
by clw8 on 3/17/16, 8:39 AM
by im_down_w_otp on 3/17/16, 9:30 PM
How do I go about sponsoring a technical writer to complete them?
by philjackson on 3/17/16, 11:46 AM
by alberth on 3/17/16, 3:57 PM
by andrewvijay on 3/17/16, 6:36 AM
by diskcat on 3/17/16, 7:04 AM
Im going to buy some spare paren keys, they might become scarce in the immediate future.