News for hackers. Stuff that matters.
Re:Three Months of Go, from a Haskeller’s perspective (2016) by fauigerzigerk on Sunday March 19, 2017 @02:22PM (#13908758)
I'm not yet familiar enough with Haskell to be honest, but languages like Scala, C++ (to the extreme) and to a lesser degree C# and Swift have a lot more support for non local redefinition of syntactic expressions than Go.

I totally agree with you about pure functions. They can be a real simplification, but only if any deviation from purity requires special syntax at the call site. Otherwise you're back in the guessing game.

Re:Three Months of Go, from a Haskeller’s perspective (2016) by chongli on Sunday March 19, 2017 @07:54PM (#13910600)
but only if any deviation from purity requires special syntax at the call site.

Haskell makes it easy to write data and function types that enforce purity at the call site, throwing a type error if you make a mistake. Not just purity though, you can restrict these types to any arbitrary set of methods of your choosing. This lets you do things like parsing a blob of JSON and having all functions that depend on the result be guaranteed not to have to deal with a failed parse or otherwise invalid data. The fact that the data is good has been encoded in the types, preventing you from passing bad data by throwing a type error.

Re:Three Months of Go, from a Haskeller’s perspective (2016) by tel on Sunday March 19, 2017 @04:32PM (#13909447)
> special syntax at the call site

Definitely Haskell's game then