S-Q-L is a lame normie version, if you are really a leet haxor you know about the obscure information that it's sequel.
I hate that I always have to look these things up to not look out of place. For example nginx is engine-ex not en-jinks. They often seem intentionally hard or ambiguous to pronounce.
It's kind of ironic because I only learned the "correct" pronunciation when I got a boring office job at an American tech company. When I used the n00b pronunciation I was in college, and way more of a 1337 h4x0r.
So as a shibboleth it mostly functions to distinguish those who discuss tech in English with their colleagues from those who do not. The latter group is quite diverse; it includes self-taught people, people communicating mostly in writing, and people who speak other languages than English with their colleagues.
> For example nginx is engine-ex not en-jinks. They often seem intentionally hard or ambiguous to pronounce.
I think it's a side-effect of the desire to create a name for your project that is both short and unique.
That is kind of funny to me because where I live the S-Q-L vs sequel divide is more along the linux/microsoft divide.
Meaning if you encounter someone here that pronounces SQL as sequel you probably found a DotNet developer or at least someone that primarily focuses on Microsoft technologies.
I have only ever heard it pronounced as "S-Q-L". When I had a customer on the phone going on about their "sequel" years ago I genuinely had no idea what they were on about, only only when they said (after a few minutes) "Microsoft sequel" did it finally click it was SQL.
I mostly have a background in Linux/Unix-y stuff, and I've hardly ever heard someone say "sequel" since, so this seems about right.
Not that I care either way, pronounce things however you like, but it sure can be confusing!
> Apache is an awkward one, because it's a Spanish loanword from Nahuatl
Probably North American native language (though there is a less-accepted theory of entirely-Spanish origin), but almost certainly not Nahuatl. Per Wikipedia, the dominant theories are Zuni and Yavapai.
The correct pronunciation of Apache is "a patchy" as in "a patchy HTTPD server". The pronunciation of the Spanish and Nahuatl etymological origins of the other side of the pun are irrelevant.
Unless you read the very next paragraph on the wikipedia article...
> Brian Behlendorf, one of the Apache's creators, asserted that the origins of Apache were not a pun, stating:
> > The name literally came out of the blue. I wish I could say that it was something fantastic, but it was out of the blue. I put it on a page and then a few months later when this project started, I pointed people to this page and said: "Hey, what do you think of that idea?" ... Someone said they liked the name and that it was a really good pun. And I was like, "A pun? What do you mean?" He said, "Well, we're building a server out of a bunch of software patches, right? So it's a patchy Web server." I went, "Oh, all right." ... When I thought of the name, no. It just sort of connotated: "Take no prisoners. Be kind of aggressive and kick some ass."
So, no, it's based on a stereotype of a group of tribes indigenous to North America. The pun endures because the indigenous culture did not.
I hate that I always have to look these things up to not look out of place. For example nginx is engine-ex not en-jinks. They often seem intentionally hard or ambiguous to pronounce.