News for hackers. Stuff that matters.
Re:Everyday hassles in Go by waps on Tuesday December 30, 2014 @10:30AM (#8814935)

  Application in Haskell is left associative so its

  ((Map String) Any)
You seem to have stumbled on the exact conflict. Anybody who's seen the theory of lambda calculus will recognize the significance of what you've written, and how it applies to partial binding of functions.

Anybody who hasn't will either be thinking of lisp or just be totally confused.

This is where the conflict is. Many developers actually know some programming theory and find Go woefully insufficient for anybody calling himself a programmer. And the ones that just fiddle around with things and make barely working programs without really knowing what they're doing are very happy that they don't have to know this in Go.

What's really going on is that people with real programming background find that Go forces them to think at the lowest possible level of abstraction, with no way up. And people without any programming background say "that's GREAT !".

Re:Everyday hassles in Go by the_af on Tuesday December 30, 2014 @02:31PM (#8816224)
I'd find it depressing if there was any programmer out there who had trouble understanding the concept of "left associativity". I think I learned it in high school.
Re:Everyday hassles in Go by Peaker on Tuesday December 30, 2014 @03:06PM (#8816440)
He's talking about the concept of currying, not left-associativity.
Re:Everyday hassles in Go by the_af on Tuesday December 30, 2014 @03:36PM (#8816598)
Original question:

> What's a parameter to what?

Answer:

> Application in Haskell is left associative so its

> ((Map String) Any)

Which looks crystal clear to me. This is also the part of the answer that user waps later quoted.