News for hackers. Stuff that matters.
Re:Asciinema 1.3 Switches from Go Back to Python by fizzbatter on Wednesday July 13, 2016 @06:23PM (#12090154)
It's funny, when using C++ or Rust, Go feels like my version of Python/Javascript/Etc. There's something very appealing of it to me.. it's the NodeJS of the Typed world to me, and i love it for that. Granted, i'm trying to switch my codebases to Rust, but still - i can't imagine going back to Node/Python/etc. But to each their own, i'm not foolish enought to say i'm "right".

With that said though, i have a hard time understanding complaints like:

> if err != nil { gets old even faster.

I may be biased, because my time in frontend JS land, but i love checking errors every time. It's a language feature to me.

Ignoring errors and expecting something else to care and catch/handle them is just.. worrying to me. Likewise,

  try
    .. stuff ..
  catch
    .. stuff ..
Gets far older to me than `if err != nil {`. But that's just me i suppose.
Re:Asciinema 1.3 Switches from Go Back to Python by framp on Wednesday July 13, 2016 @06:52PM (#12090350)
Both gets fast really soon.

Have you ever checked out Maybe (http://learnyouahaskell.com/a-fistful-of-monads#getting-our-...)?

Re:Asciinema 1.3 Switches from Go Back to Python by mrcoleman on Wednesday July 13, 2016 @07:36PM (#12090590)
I found this guy's description of the Either monad to be rather good https://fsharpforfunandprofit.com/rop/