Googling for "Math squiggle that looks like a cursive P" is not a very elegant or convenient way of learning new symbol names.
I wish every proof or equation came with a little table that gave the English pronunciation and some context for each symbol used.
It would make it a lot easier to look up tutorials & ask questions.
And never mind that cognitive load that comes from managing the use of symbols that are the "same symbol" modulo something the typeface. Trying to read something like
"Little b equals Fraktur Bold Capital B divided by (q times Cursive Capital B) all over Gothic Italic B", blah, blah... then throw in the "weird little squiggle that looks kinda like a 'p' but not quite". It's insane.
My most-used programming language is Go, but I’ve been writing mainly Swift for the past year or so. While there’s a lot I like about Swift, its verbosity leads me to waste an inordinate amount of time pondering what the correct verbiage ought to be, and I often miss Go’s more terse, often single-character naming convention.
Huh. I was expecting that comparison to go the other way given Go's notorious verbosity in terms of error handling, generics etc.. Maybe people compensate for verbosity in one area by being more concise in others (though that doesn't explain e.g. APL).
Or, I suppose you could say that Go is semantically verbose (explicit error handling, no/low use of generics, no operator overloading), but syntactically concise (short variable names). Swift is the opposite, being semantically concise (extremely heavy use of generics, default arguments) but syntactically verbose (labeled arguments, English-like clauses, result builders).