Are We There Yet?

``Simple Made Easy" presentation has sparkled a vivid discussion about state, but many people seem to miss the point completely. They either think that state isn't complex at all and doesn't need to be fixed, or that the alternatives are inherently too slow and inefficient to be taken seriously.

In his another presentation Rich talks about this topic almost exclusively and I guess it's a required watch if you want to understand the first one thoroughly.

http://www.infoq.com/presentations/Are-We-There-Yet-Rich-Hickey

>>28
Well, yes, just like any other programming language.
Other languages use "statements". Still assembly is comparable to Lisp, cuz it uses instruction pointer as a "continuation", but most compilers dont that every assembly instruction is a lambda in itself.

>>41

Other languages use "statements". Still assembly is comparable to Lisp, cuz it uses instruction pointer as a "continuation", but most compilers dont that every assembly instruction is a lambda in itself.


Holy shit are you stupid.

>>40
Byt why Haskell uses retarded buzzwords everywhere? For examle, why it calls lists "tuples"? Why Haskell calls fuctions "polymorphisms"?

>>43
Because Haskell has no real lists or functions, instead it has these limited surrogate substitutes.

>>43
Because tuples are not lists, and functions can be polymorphic in Haskell.

>>45
Yay! Tuples are crap!

>>46
Go back to reddit or /g/.

>>45
functions can be polymorphic in Haskell.
In Lisp every function is "polymorphic", that is why Lisp considered minimalistic and uniform language, while Haskell considered overengeneered piece of shit.

>>47
or
nondererminism doesnt exist.

>>48-49
>>47

>>50
Your answer shows that you're out of viable arguments. I will interpret it as your surrender.

>>51
You're back! I missed you so much. Please, don't ever leave me alone again, I can't live without you.

Lisp is shit.
Haskell is worse.

>>52

I'm getting a restraining order on you tomorrow.

Are we check 'em?

"Dubs made easy"