News for hackers. Stuff that matters.
Re:A year with Go by codygman on Friday June 05, 2015 @09:17PM (#9669174)
As someone who used Go in the past for work and now uses Haskell, I can say that the advantages of Haskell over Go are more than "just theoretical".

In my day job I use Haskell to "just get shit done". However when it comes time to refactor I can do it much faster and safer in Haskell.

The ease of refactoring creates an incentive to improve code.

Re:A year with Go by crimsonalucard on Friday June 05, 2015 @09:43PM (#9669235)
Seems like Go and other imperative languages are easier to start a project off with, but functional languages really shine when the code becomes really large and complex.
Re:A year with Go by codygman on Saturday June 06, 2015 @06:55AM (#9670377)
I can agree with that, but once you are experienced with functional languages I think "easier to start off with" becomes a very low value. I'm assuming by start off with you solely mean "starting a new project" and not "starting to use language from scratch".

At least that seems to be what has happened in my case.

Re:A year with Go by dllthomas on Saturday June 06, 2015 @02:25PM (#9671707)
I find that the confidence that refactoring will be easy helps me tremendously with velocity when starting a project.
Re:A year with Go by eloff on Saturday June 06, 2015 @11:00PM (#9673229)
My experience is the exact opposite. Maybe we work on very different kinds of problems, or maybe it's just because we're different people.
Re:A year with Go by codygman on Monday June 08, 2015 @01:28AM (#9677360)
> Maybe we work on very different kinds of problems, or maybe it's just because we're different people.

In the interest in figuring out which, what problems do you work with and what are your principles/beliefs/guiding principles in software? :P

Re:A year with Go by codygman on Saturday June 06, 2015 @11:13PM (#9673262)
I work on rest APIs mostly and the Internet of things.