http://christophermeiklejohn.com/lasp/erlang/2015/01/10/ad-c...
LASP: A Language for Distributed, Eventually Consistent Computations
21–29 of 29 posts
Re: LASP: A Language for Distributed, Eventually Consistent Computations
#22You can usually guess quality of programming language from the first page of its description. For LASP it clearly sucks. No simple example, are you kidding me? I finally dug out example at below link and all I can say is this is pretty ugly language. So many _ and curly brackets that it feels dizzy. None of the sample code is even remotely intuitively readable to make a guess what's going on. http://christophermeikle…
I've added a simple example, because I received that criticism from others, so, thanks for your feedback.
Lasp's prototypical implementation is provided as an Erlang library: this is a research language and we're researching the semantics of distributed computation and not the syntax. The syntax seen in the examples is extremely close to the syntax of the built in 'lists' module of Erlang, with the addition of having to declare types, because of Erlang's type system. This was done to make it seem natural to Erlang programmers.
(Disclaimer, I'm one of the primary authors of Lasp, @cmeik on Twitter)
Re: LASP: A Language for Distributed, Eventually Consistent Computations
#23A sample code fragment on the front page will be highly appreciated.
(Disclaimer, I'm one of the primary authors of Lasp, @cmeik on Twitter)
Re: LASP: A Language for Distributed, Eventually Consistent Computations
#24You can usually guess quality of programming language from the first page of its description. For LASP it clearly sucks. No simple example, are you kidding me? I finally dug out example at below link and all I can say is this is pretty ugly language. So many _ and curly brackets that it feels dizzy. None of the sample code is even remotely intuitively readable to make a guess what's going on. http://christophermeikle…
Re: LASP: A Language for Distributed, Eventually Consistent Computations
#25Re: LASP: A Language for Distributed, Eventually Consistent Computations
#26Re: LASP: A Language for Distributed, Eventually Consistent Computations
#27Commutative, 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/in…
Re: LASP: A Language for Distributed, Eventually Consistent Computations
#28Commutative, 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/in…
Re: LASP: A Language for Distributed, Eventually Consistent Computations
#29You can usually guess quality of programming language from the first page of its description. For LASP it clearly sucks. No simple example, are you kidding me? I finally dug out example at below link and all I can say is this is pretty ugly language. So many _ and curly brackets that it feels dizzy. None of the sample code is even remotely intuitively readable to make a guess what's going on. http://christophermeikle…