• kaffiene@lemmy.world
    link
    fedilink
    English
    arrow-up
    26
    arrow-down
    1
    ·
    7 months ago

    My favourite is “all the boilerplate” then they come up with go’s error checking where you repeat the same three lines after every function call so that 60% of your code is the same lines orlf error checking over and over

    • pulaskiwasright@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 months ago

      And god help you if you forget those 3 lines somewhere and you silently have database failures or something else.

      • kaffiene@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        7 months ago

        Yeah, that’s the other thing - it does become easier to accidentally fail to deal with errors and the go adherents say they do all of that verbose BS to make error handling more robust. I actually like go, but there’s so much BS with ignoring the pain points in the language.

    • xtapa@discuss.tchncs.de
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      7 months ago

      When you handle all your errs the same way, I’d say you’re doing something wrong. You can build some pretty strong err trace wrapping errs. I also think it’s more readable than the average try catch block.

      • kaffiene@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        7 months ago

        You still need to add error handling to every call to every function that might raise an error