<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 25, 2014 at 1:37 PM, Garrett Smith <span dir="ltr"><<a href="mailto:g@rre.tt" target="_blank">g@rre.tt</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, Sep 25, 2014 at 12:00 PM, Lloyd R. Prentice<br>
<<a href="mailto:lloyd@writersglen.com">lloyd@writersglen.com</a>> wrote:<br></span><span class=""><br></span></blockquote><div><snip></div><div>Â </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
> - And, finally, during waning minutes of the party, Garrett Smith told me that Erlang should be completely rewritten from the ground up. He's tried with e2, but there's no interest.<br>
<br>
</span>You forgot to mention that Garrett was stammering drunk and shouting<br>
for Vinoski, saying he wanted to "teach that dirty scheduler writing<br>
scoundrel a lesson he'd not soon forget!"<br>
<br>
But to clarify, I did not say that Erlang should be rewritten, but<br>
that some other new distribution, built atop the Erlang VM and<br>
toolchain (similar to what Elixir has done), could be created that<br>
cleaned up the core libraries and was free from legacy restrictions.<br>
<br>
I personally like Erlang as it is -- I don't want a new language (like<br>
Elixir). But I recognize that the legacy of Erlang prevents it from<br>
moving aggressively into a more newbie friendly and accessible form.<br>
That's a matter of physics, not politics, religion, or personal taste.<br>
Erlang will continue to improve incrementally, but it will never enjoy<br>
the freedom to build-from-scratch that Elixir has. But something new<br>
*could*.<br>
<br>
The problem, obviously I think, is the breathtaking cost of "rewriting<br>
Erlang". This is a vision that is not likely possible. But one can<br>
drink and ponder.<br>
<br>
I have proposed a new language called Lamprey:<br>
<br>
<a href="https://github.com/gar1t/lamprey" target="_blank">https://github.com/gar1t/lamprey</a><br>
<br>
This doesn't exist. It's mostly a joke and I don't even know if it's<br>
possible. But if it came to be, it would be epic in the history of<br>
languages.<br>
<br>
The idea is to take the stunning and amazing work of the Elixir<br>
community and bring it back to Erlang syntax as a new language --<br>
Lamprey. Lamprey would enjoy clean libraries, documentation, tools,<br>
etc. without doing any work. When a new version of Elixir is released,<br>
Lamprey would just run its bash scripts to convert everything back to<br>
Erlang, and whamo - a new release of Lamprey!<br>
<br>
Parasitism at the computer language level.<br>
<br>
Robert Virding btw gets credit for the name :)<br>
<br>
Thanks Lloyd for attending on Monday. It was a pleasure to finally meet you!<br>
<span class="HOEnZb"><font color="#888888"><br>
Garrett<br></font></span></blockquote><div><br></div><div><br></div><div>Funny you should mention all that; I've been thinking about something similar lately. Port Elixir back to Erlang syntax  so that it can compile .erl files but bring along interesting Elixir features (interesting to me is metaprogramming, pipe operator, module system.)  I named it "Still". It's "still" just erlang with alchemical homage to elixir.</div><div><br></div><div>I was also at the conference; thank you for all the hard work that went into this fantastic event!</div><div><br></div><div><br></div></div></div></div>