111–120 of 217 posts
"Google is an amazing company, and there's some really great technologists working there," he said. "But fundamentally, their business model is different and they're not known for shipping consumer experiences that are used by hundreds of millions of people." What does he mean by this? Google search and Android are both used by more than a billion people. YouTube over 2 billion. These are all bigger than any Apple pr…
"Google is an amazing company, and there's some really great technologists working there," he said. "But fundamentally, their business model is different and they're not known for shipping consumer experiences that are used by hundreds of millions of people." What does he mean by this? Google search and Android are both used by more than a billion people. YouTube over 2 billion. These are all bigger than any Apple pr…
Earlier quoted context omitted.
I recently discovered a neat trick for fixing the duck problem, that is, adding swear words to the iOS dictionary: add a contact with the chosen words in the name fields. E.g. I have a contact named "shit shitty fuck fuckin fucking oh shit"
I find it both amusing and ridiculous that you have to go to such great lengths to be able to type a good swear word on the iphone.
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, forcin…
I'm bilingual and write approximately the same amount of messages in both languages using iOS. Autocorrect always suggests words from BOTH languages mid sentence. Like what the hell, they should be able to infer which language I'm using just from the first word.
You can't be AI leader when every AI leader is staying away from you by 10ft pole. When Ian Goodfellow joined Apple, there was literally rain of criticism on him from ending his career as researcher to bowing down to money. I don't know of any researcher who does want to have continued research career willing to join Apple. They simply don't allow that kind of freedom or publishing results. While Apple has some stron…
Of course, the Sculley/Spindler/Amelio Apple seemed to be far more open regarding research than the Jobs- and Cook-era Apple. Jobs closed down the labs in 1997 and help institute Apple's famous culture of secrecy that persists today.
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, forcin…
I've recently switched back to iOS and hoped this behaviour was temporary as it got to learn my swiping style. Gboard on Android is almost perfect.
I have 3 languages on my keyboard and sometimes it suggests an autocomplete in the wrong language.
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, forcin…
To be fair, the android keyboards (like Gboard, googles own) are also bad. It's a tough problem for sure, but they haven't gotten better for the last 6-7 years at least, in my experience, and that is the point of the parent post I guess.
However, SwiftKey might be more conservative and feels a bit slower at times, but its autocorrect and prediction do a really good and consistent job.
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, forcin…
I once mentioned the rapper xxxtentacion in a text message. Now whenever I sign of an email or text to my wife with an ‘x’ iOS decides that what I actually meant to do was write ‘xxxtentacion’ and I’ve normally pressed send before I notice. After a couple of years now this is just how I talk to my wife.
It's just pathetic nonsense to congratulate anyone on this level of nonsense.
Earlier quoted context omitted.
The one the drives me mad the most is when I type a word which it incorrectly autocorrects to a proper noun (which gets capitalised), I then use backspace to delete that word and type the - completely different - correct one, but it insists on upper-casing the first letter to match the original casing of the incorrect autocorrect. It really should keep track of the fact that it introduces the case-change and invalida…
I can never make iOS write “Hong Kong” when swipe-typing; tried setting up forced text replacement entry (kong->Kong) to zero effect. It is always “Hong kong”.
PS: iOS just did this twice while typing this reply.