Hacker News Reader

Comment by RcouF1uZ4gsC | Hacker News Reader

You are missing the forrest for the trees.

When people refer to a language, most often they are using it as a synecdoche to refer to the whole language ecosystem and not just the the formal language definition.

If you look at the Python ecosystem, it is most definitely interpreted.

View on HN

Off topic, but thank you for introducing the word "synecdoche" to me.

Movie recommendation: Synecdoche New York

Now the question for non-native speakers is: How to pronounce that word? ;D

Sin-eck-da-key

Or at least, that's how I'm hearing it from Google.

I'd pronounce it See-Neh-Doal-Kee

there is no L in it

L sounds like a short "OO" in Brazilian Portuguese, and he asked how a non-native would pronounce it...

Exactly

Did you look up how to pronounce it? I was mispronouncing it for like a year after seeing “Synecdoche New York” (it’s kinda pretentious, not for everyone). My coworker laughed at me when I said the name to him. I’d only ever seen it written, and did not look at a pronunciation chart. Wah wah.

Just in case anyone else is getting it wrong like I was …

https://youtube.com/watch?v=v-n1vGeVIXo

(But really, https://youtu.be/u8_LDxZReTc)

Personally, I often find myself saying things like "the <lang> ecosystem" to avoid this.

I think it is fair to have a discussion about terminology and arguing with the actual meaning of terms. When there is a technical difference, it would be good to acknowledge that difference between terms. It does not hurt anyone to do that. One can still say something like: "When we communicate I will use the word x for meaning y, because it is shorter and more convenient."

Reply on news.ycombinator.com