I don’t think it makes any sense to keep investing in an old language, while writing code for today.

Which make me ask, will it ever be ported/modernized?

  • graynk@discuss.tchncs.de
    link
    fedilink
    arrow-up
    2
    ·
    3 hours ago

    Guess what is and what isn’t used in serverless functions, Lambda doesn’t even support Go ffs. It’s java, ruby, node and python. And from those most use node or python.

    I assume that this isn’t bait, so I’ll answer.

    1. It doesn’t matter what Lambda supports
    2. There isn’t a dedicated runtime for Go because it doesn’t need a runtime. It will work on OS-only runtime like any other language that gets compiled down to a binary: https://docs.aws.amazon.com/lambda/latest/dg/runtimes-provided.html
    • Fushuan [he/him]@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      1
      ·
      24 minutes ago

      About 1, I was commenting on the serverless world, a big part of today’s cloud infrastructure, and AWS is one of the major cloud providers. I feel like, to show the relevance of a language compared to another, it kinda does matter that you can’t code directly and let the provider compile your small-ish program.

      About 2, it works with the generic runtime for sure, but almost everything does, technically C++ does too lol, meaning that you need to upload the binary that you compile locally or via some sort of pipeline. Which is worse than say, using typescript and letting them transpiled it into is so Node can run it. It’s not supported in that way.

      In any case, you wouldn’t really use a compiled language like Go to have small-ish serverless functions. Go does have a use case ofc, I’m just making a case of how not obsolete python is.