nginx (“engine x”) is an HTTP web server, reverse proxy, content cache, load balancer, TCP/UDP proxy server, and mail proxy server. […] [1]

I still pronounce it as “n-jinx” in my head.

References
  1. Title (website): “nginx”. Publisher: NGINX. Accessed: 2025-02-26T23:25Z. URI: https://nginx.org/en/.
    • §“nginx”. ¶1.
  • lmmarsano@lemmynsfw.comEnglish
    0·
    2 months ago

    You seem in irrational need for validation of your pronunciation despite clear justification against it. Cool ad populum. Fly that insecurity flag high.

    • rishado@lemmy.world
      0·
      2 months ago

      Buddy. The inventor’s intention is not clear justification. Language becomes what is most colloquially used. You’ll be dying on this hill 20 years from now. You argue like a redditor, insufferable

      • lmmarsano@lemmynsfw.comEnglish
        0·
        2 months ago

        There’s the original pronunciation, the suggestive spelling, the common phenomenon of punning in programming, and the natural way people pronounce it as a familiar name when they first see it. Then there’s your camp with a mythical, dorky pronunciation they pull out of nowhere and reinforce because.

        I think people are fine to call it Jason & drive you irrationally mad.

        • rishado@lemmy.world
          0·
          2 months ago

          No, there’s only two categories here.

          The original pronunciation, Jason, and the natural way, being jaysawn. Literally acknowledged by Crawford:

          “Douglas Crockford, who named and promoted the JSON format, says it’s pronounced like the name Jason. But somehow, ‘JAY-sawn’[note 1] seems to have become more common in the technical community.”

          I wonder why it became more common? Could it be that jay-sawn is the “natural way people pronounce it”? No, it must be a bunch of dorks that pronounce it wrong just because, right?