LASP: A Language for Distributed, Eventually Consistent Computations
1–10 of 29 posts
Re: LASP: A Language for Distributed, Eventually Consistent Computations
#2I'm kind of disappointed that with a name like LASP, it doesn't have lisp syntax.
Re: LASP: A Language for Distributed, Eventually Consistent Computations
#3I'm kind of disappointed that with a name like LASP, it doesn't have lisp syntax.
Apparently it's not even really a "language" in the same way most articles mean, but simply an Erlang library.
Re: LASP: A Language for Distributed, Eventually Consistent Computations
#4Re: LASP: A Language for Distributed, Eventually Consistent Computations
#5Earlier quoted context omitted.
Apparently it's not even really a "language" in the same way most articles mean, but simply an Erlang library.
Which is good, because there already are way too many languages...
Could you elaborate on the drawbacks of having "too many languages"?
I thought that it was commonly accepted that having a diverse ecosystem of programming languages was good thing for everyone (Companies and engineers) because it fostered and fueled innovation in more mainstream languages by showing that feature X is relevant, or possible or desired by the community.
I sincerely don't see how it could be a problem? You can just ignore the bad ones or those that don't suit your needs while enjoying the others. Also, I might be mistaken but I am under the impression that new PLs have faster iteration cycles and are more receptive to feedback to suit one's particular needs.
I personally enjoy to see a new programming language makes the front page of HN because they often try to address existing problems in current big PLs, in a new way or incorporate state of the art PL theory concepts that I did not know!
Edit: why the downvotes? This is a genuine question!
Re: LASP: A Language for Distributed, Eventually Consistent Computations
#6Commutative, Conflict-free, Convergent -- the 'C' in CRDT sure is flexible. :)
Re: LASP: A Language for Distributed, Eventually Consistent Computations
#7Earlier quoted context omitted.
Apparently it's not even really a "language" in the same way most articles mean, but simply an Erlang library.
Which is good, because there already are way too many languages...
Disagree. Maybe there's too many popular ones but I can't imagine there ever being too many toy ones. We're nowhere need figuring out how to make a perfect language. It takes a lot of trial and error to continue to improve.
Re: LASP: A Language for Distributed, Eventually Consistent Computations
#8I'm kind of disappointed that with a name like LASP, it doesn't have lisp syntax.
As we note in the full paper that will be presented as part of PPDP 2015 [1]:
"Inspired by LISP’s etymology of “LISt Processing”, our fundamental data structure is a join-semilattice, hence Lasp."
(Disclaimer, I'm one of the primary authors of Lasp, @cmeik on Twitter)
Re: LASP: A Language for Distributed, Eventually Consistent Computations
#9I'm kind of disappointed that with a name like LASP, it doesn't have lisp syntax.
Apparently it's not even really a "language" in the same way most articles mean, but simply an Erlang library.
The Erlang library is a prototypical implementation of the programming model. It's a research project, and this allows us to quickly prototype and experiment with the model as we see what works and what doesn't. It's not meant for production use.
The paper that will be presented as part of PPDP 2015 [1] will contain language semantics for a subset of the operations in the language (and we will continue to provide these, with the end goal of having a standalone language.)
(Disclaimer, I'm one of the primary authors of Lasp, @cmeik on Twitter)
Re: LASP: A Language for Distributed, Eventually Consistent Computations
#10Commutative, Conflict-free, Convergent -- the 'C' in CRDT sure is flexible. :)
(edited for formatting)
Commutative (operation-based) and convergent (state-based) have been grouped under the more general term conflict-free.
In 2011, Shapiro et al. [2] showed equivalence between the two types, and later the name was generalized [3]. I've compiled a list of CRDT related resources for more information. [1]
[1] http://christophermeiklejohn.com/crdt/2014/07/22/readings-in...
[2] http://hal.upmc.fr/inria-00555588/document
[3] http://dl.acm.org/citation.cfm?id=2050642
(Disclaimer, I'm one of the primary authors of Lasp, @cmeik on Twitter)