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
- Title (website): “nginx”. Publisher: NGINX. Accessed: 2025-02-26T23:25Z. URI: https://nginx.org/en/.
- §“nginx”. ¶1.
Didn’t realize I was buddies with 99% of everyone that’s interacted with JSON!
Also didn’t know people used the term ‘plebs’ unironically, you sound like an absolute joy to be around
You seem in irrational need for validation of your pronunciation despite clear justification against it. Cool ad populum. Fly that insecurity flag high.
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
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.
No, there’s only two categories here.
The original pronunciation, Jason, and the natural way, being jaysawn. Literally acknowledged by Crawford:
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?
Yep: I often see people try to “correct” learners at bootcamps pronouncing it Jason. The fact people pronounce it Jason until told otherwise tells us which is more natural. The “correction”, in contrast, is a myth that must be learned.
Acknowledging something happens doesn’t endorse it, and Crawford never endorsed your pronunciation as natural. As I suggested earlier, he said “I strictly don’t care”. Jason is a completely reasonable & natural pronunciation.