Live data from Hacker News

LASP: A Language for Distributed, Eventually Consistent Computations

lasp-lang.org

21–29 of 29 posts

Re: LASP: A Language for Distributed, Eventually Consistent Computations

#21
You 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://christophermeiklejohn.com/lasp/erlang/2015/01/10/ad-c...

Re: LASP: A Language for Distributed, Eventually Consistent Computations

#22
post #21

You 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…

The syntax you're complaining about is Erlang's. (_ is to ignore a token in a pattern match, braces denote tuples.)

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

#24
post #21

You 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…

Please don't post comments to HN that dismiss new work so nastily. There are many ways of suggesting improvements that don't involve trampling all over someone's freshly planted garden.

Re: LASP: A Language for Distributed, Eventually Consistent Computations

#25
post #3

I'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.

Similar to MapReduce in that respect. A library that supports a computational model.

Re: LASP: A Language for Distributed, Eventually Consistent Computations

#26
post #3

I'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.

How is it not really a language?

Re: LASP: A Language for Distributed, Eventually Consistent Computations

#27
post #6

Commutative, 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…

Thanks, this was useful!

Re: LASP: A Language for Distributed, Eventually Consistent Computations

#28
post #6

Commutative, 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…

[deleted]

Re: LASP: A Language for Distributed, Eventually Consistent Computations

#29
post #21

You 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…

Aaaahhhh, the syntax is different! Help, help, the world is coming to an end.
Post reply on HN