Re: Have you read SICP

Why should I believe you, or follow a link from someone in their first 10 posts? Why is that book worth reading? What does SICP stand for?

Hmm, at least the link seems to be honest (pointing where it appears to point).

Thanks.

Dear lel-kun
I would like to inform you that >>39-kun said nothing about lisp sucking nor about disliking lisp
Thank you for your attention and have a nice UTC night

>>41

*lel-kunt

Bump because http://bbs.progrider.org/prog/read/1406042958/16 is a nigger

>>43
I'm the nigger of that thread and curse you fuckers

>>44
`>44
>dubs

nice :^)

>>37

IQs above 160

Doesn't mean anything.

>>38

OCaml

Half-baked shit on so many levels I don't even want to elaborate.

ML derivative languages

Shitty superfluous syntax. fun fun fun val | +| val fun &| | |

Significant whitespace

Is excellent and help keep syntax concise. You're free to use curly-brace shit, though.

The IO monad

At least a basic level of side effects control. Most languages don't have even that.

the IO monad, which serializes everything

What the fuck are you stupid whore blabbering about? Do you even know what "serialization" means?

The advantage is .. unclear

Clean and concise expression of common computational patterns (e.g. "computations that can fail" are very cleanly expressed in the Maybe or Either monads). Also control of the effects any particular piece of code can and cannot invoke.

Unexpressive FFI

Don't know about that, but Haskell has most of things needed from C (like mutable unboxed arrays) built in.

Laziness .. should not be the default. It’s not how any real computers work

Why should the programmer give a shit how "real computers" work? Computers should serve people, not the other way around.

Lack of optional/labelled args

Just use Maybes.

Haskell is widely studied and often pimped, but not used very much

Just go to Hackage or Planet Haskell, you'll see that Haskell is used heavily, in industry too. The ecosystem is quite mature, and people use Haskell for anything from databases to games to websites to you name it.

>>47
Can't reply to more than a dozen words at a time?

Haskell is used by retards and lisp by people who know what they are doing. Haskell is the functional equivalent of java (shit).

>>49
The sheer number of research papers centered around Haskell and the absence of corresponding Lisp papers proves the reverse.

Oh and Lisp isn't even functional. Lisp is the stillborn equivalent of Ruby (shit).

>>50
Actually the only Lisp that is used today is just a Javashit library, not Ruby.

>>50,51
The lisp envy is strong.

Ruby version
f = get_some_anonymous_function
f.call

Common Lisp
(let ((f (get-some-anonymous-function)))
(funcall f))))))))))))))))))))))))))

Similarities
- Functions are no first class citizens (you can't call anonymous functions directly)
- Both suck
- GC

Differences
- syntax))))))))))

They are pretty much the same.

>>53
No life loser ;). Go to bed. Your lisp envy is strong.

>>54

Go to bed.

It's morning here now you prick.

>>55
Up all night? First thing you do is go on here? What a life. lisp envy ;)

>>52

shit envy

Not everyone is a coprophile like you.

Lewin reported that "... consumption of fresh, warm camel feces has been recommended by Bedouins as a remedy for bacterial dysentery; its efficacy (probably attributable to the antibiotic subtilisin from Bacillus subtilis) was confirmed by German soldiers in Africa during World War II".

I read the first chapter, am I an ^expert_programmer?

>>59
So you can now add two numbers together with Scheme? Sure... that makes you an expert programmer.

I made a 2-bit adder out of relays, LEDs, switches, and a 9-volt battery. Try doing that in Scheme, you know-nothing little cocksuckers.

>>61
I made millions of 2-bit adders in Scheme. Try doing that with relays, LEDs, switches and 9-volt batteries, you know-nothing little cocksucker.

The fact is Haskell is (currently) not a good platform for a web application. Modern web applications today are typically fairly thin 'proxies' between the data and heavy logic - Haskell is not ideal for this due to the ghastly interfaces to persistence available, purity, performance.

What happens on a GET request for some REST API endpoint in a haskell web application?

Haskell cheats on purity for read -> cheats on types for json to haskell -> cheats again on types for haskell to persistence -> cheats again on purity for read from persistence -> does the same thing again backwards. Point? You end up ignoring most of what makes Haskell awesome anyway.