• OsrsNeedsF2P@lemmy.mlOP
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      100% serious, because my next job uses Go - Why? Everything is painful and takes way more code than it should.

      • adriator@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Its compiler is very fast, the libraries are great, importing new packages is easy and straightforward, HTTP libraries and frameworks are some of the best I’ve worked with.

        Compared to Java or C#, there really isn’t that much boilerplate.

        • 1hitsong@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          I’d take C# over Go any day.

          You call a function, check for err. You call a function, check for err. You call a function, check for err. You parse a string to a number, check for err.

          Some of the ugliest code I’ve worked in. Just give me a try catch!

          Is it fast! I’ll give it that.

        • invisi1407@feddit.dk
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          1 year ago

          Why is “the compiler is very fast” a good argument though? I’d rather the compiler spends 1 minute and does it well and optimized instead of 10 seconds and I have to write Go, honestly.

          In many cases, for many things, compiling isn’t the part that takes the longest in development anyway.

          There are some great aspects to Go, like how you can map fields of a struct to json properties for Marshal/Unmarshalling and channels is an interesting idea, but other than that it doesn’t seem to me like there’s a lot of pros over, say, C# which is almost ubiquitous in many industries these days.

  • MajorHavoc@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    make is inevitable, because everything is a dependency.

    There is no wisdom, no truth, only endless dependencies. /s