Re:Show HN: Python framework is faster than Golang Fiber
by nvrspyx on Tuesday January 10, 2023 @08:06AM
(#34324233)
Off topic, but thank you for introducing the word "synecdoche" to me.
Re:Show HN: Python framework is faster than Golang Fiber
by j33zusjuice on Tuesday January 10, 2023 @08:29AM
(#34324528)
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)
Re:Show HN: Python framework is faster than Golang Fiber
by narcraft on Tuesday January 10, 2023 @08:22AM
(#34324439)
Movie recommendation: Synecdoche New York
Re:Show HN: Python framework is faster than Golang Fiber
by zelphirkalt on Tuesday January 10, 2023 @08:24AM
(#34324469)
Now the question for non-native speakers is: How to pronounce that word? ;D
Re:Show HN: Python framework is faster than Golang Fiber
by nvrspyx on Tuesday January 10, 2023 @08:28AM
(#34324521)
Sin-eck-da-key
Or at least, that's how I'm hearing it from Google.
Re:Show HN: Python framework is faster than Golang Fiber
by drowsspa on Tuesday January 10, 2023 @08:45AM
(#34324744)
I'd pronounce it See-Neh-Doal-Kee
Re:Show HN: Python framework is faster than Golang Fiber
by aliqot on Tuesday January 10, 2023 @09:04AM
(#34324985)
there is no L in it
Re:Show HN: Python framework is faster than Golang Fiber
by drowsspa on Tuesday January 10, 2023 @10:14AM
(#34326020)
L sounds like a short "OO" in Brazilian Portuguese, and he asked how a non-native would pronounce it...
Re:Show HN: Python framework is faster than Golang Fiber
by cirospaciari on Wednesday January 11, 2023 @04:26AM
(#34336684)
Exactly
Re:Show HN: Python framework is faster than Golang Fiber
by zelphirkalt on Tuesday January 10, 2023 @08:27AM
(#34324506)
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."
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.