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.
You seem in irrational need for validation of your pronunciation despite clear justification against it. Cool ad populum. Fly that insecurity flag high.
You & your buddies can keep pronouncing it jaysawn & sounding like complete dorks if it makes you feel better. However, it was clearly intended to be pronounced naturally as Jason like its inventor pronounces it.
Believing otherwise is almost as bad as the plebs who think the symbol ∅ is inspired by Greek letter φ instead of Scandinavian letter Ø.
No, it’s pronounced Jason. Douglas Crockford was just too laissez-faire to correct anyone on it probably because he didn’t give a fuck.
Elisp has a nice notation for maintainably composing regexes like any other programming expression.
Only language I’ve seen offer that.
So instead of "/\\*\\(?:[^*]\\|\\*[^/]\\)*\\*+/", the regular expression to match C block comments could be expressed (with inline comments)
(rx "/*" ; Initial /*
(zero-or-more
(or (not (any "*")) ; Either non-*,
(seq "*" ; or * followed by
(not (any "/"))))) ; non-/
(one-or-more "*") ; At least one star,
"/") ; and the final /
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.