oubiwann

Not only that, but an hour after your post, someone (burma-shave) had updated the LFE formula for v1.0 of LFE: * https://github.com/Homebrew/homebrew/blob/f95c192d43d9a56bda...

Having used early versions of Mathematica in university, I'm actually a huge fan of Maxima (a fork of Macsyma, the latter having been the principle inspiration behind Mathematica). I have it installed on several systems and use it now for all the things I used to use Mathematica. In fact, the CL source code for rational numbers in Maxima formed the basis of similar work in LFE (the horatio project).

I was very sad to find out that Xlisp-Stat had not been ported and maintained in CL :-/ ... perhaps a good project for a motivated, if fringe, *SoC project :-)

"Macro handling as god intended."

I had to laugh :-) That reads like it's out of the Moonual ...

I have the LISP-STAT book by Luke Tierney on my desk right now. Love it :-)

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.

It's a work in progress, but this might be useful:

* http://lfex.github.io/hyperpolyglot/

Oh, wow -- that's a great tidbit! I hadn't heard that before, Robert (one for the LFE Lore files ...)

So a couple of comments here :-) Robert is actually an old-school Lisper (and a hard-core one, too). LFE has been inspired not only by CL but also Maclisp. The point being that, yeah, he's an Erlang guy, but he was first a Lisp guy (and has always remained so).

Second comment: LFE is a Lisp, but it's a Lisp whose first and foremost goal was to allow one to build fully Erlang (and OTP)-compatible systems in Lisp. Clojure's Lisp has a Java flavour; LFE's Lisp has an Erlang flavour. They are both very real and compelling Lisps :-)

@technomancy, Hey man! Good to see you here ... but not even a little love for a Lisp-2? ;-)

We've chatted about this before, and I guess I just got used to (funcall ...) in CL. There's no question, though, that being able to call functions without that is very clean.

You know, if you squint just right, the name/arity uniqueness in Erlang is a pretty nice match for a Lisp-2 ;-)

That's very cool :-) I think rvirding would approve ;-)

Did you ever check out LFE afterwards. to compare your approach with Robert's?

Frank's been doing all his latest work on the Raspberry Pi, actually. In fact, that's what he tested the new LFE support on :-)

Frank's also going to be giving a talk at Erlang Factory SF this year -- but this time on the Nerves Project itself :-)

If you're going to be handling large amounts of data, then Disco is what you'd want to use, not this.

However, if you're spending your day in an LFE REPL and want to be able to parallelize computation out to multiple Python instances, then this tool will be for you ("will be" because parallelization is in the queue: https://github.com/lfex/py/issues/38).

As things stand right now (without parallelization), this library means that Erlang, Elixir, LFE, Joxa, etc., hackers don't have to context switch out of their preferred mode into another language, but can do it from the comfort of their regular daily routine. (I know Erlang hackers who refuse to fire up a Python interpreter...)

In other words, this is very much like an IPython for the Erlang world (where the ZeroMQ messaging architecture of IPython isn't needed, since that all comes for free in Erlang).

Bingo.

The points made below about Disco a great. Similar confusion came up on Twitter with regard to CloudI. As a result of that, I updated the README with clarification on what LFE py is not for, and what you might use in those cases.

Disco is brilliant stuff (I greatly prefer to to Hadoop), and the fact that it has a distributed file system should really clarify its use cases (any why one would choose to use it over something life LFE py which doesn't have one!).

(As you can see, I can't help myself from saying great things about Disco :-))

Disco has gone beyond MR with pipelines, too. This allows for more generalized workflows. Great stuff.

Nice that you mention Pandas ... it's on the list for being supported by lsci (which in turn will be using LFE py).

As for Hy: LFE py comes with custom ErlPort encoders/decoders, and I came this close to writing those in Hy. However, I did want anyone with a Python background to be able to easily read and contribute, not just Lispers ;-)

Regardless, it would be nice to use with Hy (and probably trivial: a requirements.txt update, and then adding some Hy modules in ./python/lfe, at which point you should be able to access them from LFE).

I've update the blog post with these, but here they are in this context as well:

* A more detailed follow-up to that post is here: http://blog.lfe.io/tutorials/2014/12/03/1828-erlport-and-pyt...

* There's now an even easier way to use Python from Erlang/LFE that wraps ErlPort: https://github.com/lfex/py

Also, the original post was re-blogged here, where the code is much more legible: http://blog.lfe.io/tutorials/2014/11/21/1508-erlport-using-p...

Yeah, the quick start is just intended to get folks going. The "Docs" page definitely has a lot more useful stuff there!