3 ms·
When I have to say SQLite out loud, my brain decides in the moment between "ess-cue-lite" and "see-cue-lite." I have no idea what criteria/heuristics I use in t
by quickslowdown 3y ago
When I have to say SQLite out loud, my brain decides in the moment between "ess-cue-lite" and "see-cue-lite." I have no idea what criteria/heuristics I use in that moment to decide which way to pronounce it, but for whatever reason that's how it works for me.
In my head I feel like I say "ess-cue-lite" pretty much every time.
- chrisweekly 3y agohuh, I get the "ess-cue-lite" but not (at all) the "see-cue-lite" -- for me, the "see" sound only makes sense in the context of "sequel" (see-kwell-ite), which is how I instinctively tend to pronounce it.
- quickslowdown 3y agoTo confound you further, I say "sequel" and not "ess-cue-ell" for SQL
- smaudet 3y agoI think the former pronunciation is more correct, but... I see the point of the later if you are prone to verbalize acronyms: SQL => Verbalized Acronym: "See-Quell" vs Structured Query Language: "Ess-Queue-Ell" So then See-Cue-lite is a concatenation of the verbalization with the "lite". Whereas Ess-Cue-Lite is a concatenation of the acronym pronunciation with the "lite". This probably solve the former question of why some people say both and don't understand why. If the conversation/person is saying "SeeQuel" and "Sass" or "less" etc. then "See-Cue-Lite" fits that dialect. In a dialog with a lot of acronyms e.g. SQS, VPN, AWS, etc. you are probably more likely to go the acronym route i.e. "Ess-Cue-Lite". The term itself is a bastardization of an acronym and the "lite" term, I'd argue there's no correct pronunciation.