Setting aside all the other work Apple is doing in this area, can someone explain why iMessage autocorrect is unacceptably bad (to put it diplomatically) in the era of weapons-grade language models?
Its behavior is totally bizarre. It’s like an underpowered chess engine that makes flagrant blunders: capitalizing random words in the middle of a sentence (rock -> Rock), the context sensitivity of an actual rock, forcing the same correction multiple times (i.e. you go back to fix its error, and it defiantly repeats it), contraction mixups, blindness to off-by-one-keystroke errors (consentuallt -> <no action>), and of course the occasional random word substitution. Only martial artists want to duck people (and it—no joke—just now substituted [duck -> suck]. You had one job autocorrect.)
Is this just me? Is it actually 2020? What is going on?
Its behavior is totally bizarre. It’s like an underpowered chess engine that makes flagrant blunders: capitalizing random words in the middle of a sentence (rock -> Rock), the context sensitivity of an actual rock, forcing the same correction multiple times (i.e. you go back to fix its error, and it defiantly repeats it), contraction mixups, blindness to off-by-one-keystroke errors (consentuallt -> <no action>), and of course the occasional random word substitution. Only martial artists want to duck people (and it—no joke—just now substituted [duck -> suck]. You had one job autocorrect.)
Is this just me? Is it actually 2020? What is going on?