> no one feels a pressure to use a modern term that might have less perceived value-- to say "functions" or "features" instead of "complications
Methods in OOP. Every term in functional programming. Rolex does a little bit of the Apple game, renaming jargon. But the watch industry mostly uses the term the first person to use it deployed. (“Complications” makes more sense than “features” when working multilingual across French, German and Italian.)
I’d also argue that “features” is a bit misleading. Complications aren’t about utility. They’re about art. It’s intentionally overcomplicating something.
> Complications aren’t about utility. They’re about art. It’s intentionally overcomplicating something.
This is not the original usage; "complication" does not imply "grande complication."
> ..."features"...
None of your criticism applies to "functions" which is the first term used.
> Methods in OOP. Every term in functional programming.
Yes... I'm saying in a niche, luxury industry based upon exclusivity and tradition, the marketing pushes towards old, foreign, and exotic language. All these things in commodity digital watches are "modules" and "functions" instead of "calibre" and "complications." (With Apple, on the high end, choosing "complication" for some reason ;).
Methods in OOP. Every term in functional programming. Rolex does a little bit of the Apple game, renaming jargon. But the watch industry mostly uses the term the first person to use it deployed. (“Complications” makes more sense than “features” when working multilingual across French, German and Italian.)
I’d also argue that “features” is a bit misleading. Complications aren’t about utility. They’re about art. It’s intentionally overcomplicating something.