Always choose the right tool for the job? Nah. I use Go basically everywhere, which either makes me insightful or stupid. Decide for yourself! :D

  • iluminae@lemmy.world
    link
    fedilink
    arrow-up
    11
    ·
    2 months ago

    In a professional setting, sometimes the cost of developing something more performant in C is not worth it. The velocity unlocked by creating systems in Go is just incredible, after your company has built everything in C[++] for decades. I find myself creating gRPC APIs in Go to solve most design challenges, because it’s stupid fast to develop and is fairly maintainable after.

  • BmeBenji@lemm.ee
    link
    fedilink
    arrow-up
    3
    ·
    2 months ago

    I learned C++ in my first handful of programming classes. The only other languages I learned for other classes included javascript, PHP, and MySQL. I was assigned a project to be written in Java but never learned the details of the language.

    At my current job, the system I work on mostly is all Go, and while I now know Go interfaces are not as novel as I did when I first learned they existed (because I had to learn Go), the mechanisms in Go for interfaces and goroutines just feel so cool to me that I can absolutely envision myself wanting to build anything well-suited for OOP in Go.

    But that would require me to be passionate enough about programming to want to do it more than 40 hours per week lol

  • BatmanAoD@programming.dev
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    2 months ago

    I agree with everything in the article, which makes it all the more unfortunate that I really detest Go as a language.

    (It’s getting better, though.)