• Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.

Apple Watch burning a CD.

I turned off auto-correct, it's more wrong than it is right.  I'm tired of it.  And I don't mean Siri because I turned it off, but the OS itself.  Incorrectly changing "they're" to "their" and vice versa, or "too" and "to," or "its" and "it's."

I've now realized that an entire generation of people who grew up texting shorthand and have no idea how to spell are now writing the source code to the operating system. :/

 
I turned off auto-correct, it's more wrong than it is right.  I'm tired of it.  And I don't mean Siri because I turned it off, but the OS itself.  Incorrectly changing "they're" to "their" and vice versa, or "too" and "to," or "its" and "it's."

I've now realized that an entire generation of people who grew up texting shorthand and have no idea how to spell are now writing the source code to the operating system. :/
Definitely.

This might help explain why Windows 10 is so iffy much of the time. The only reason it works at all is likely because most of the core OS (kernel, etc.) is still based on legacy code from the 90s, written by people who actually knew how to spell properly.

I think the current state of our educational system is helping contribute to this, as I've noticed that in recent years, people seem like they tend to be less literate, and have less good critical thinking skills than in the past. I could go on, but it'd be too political :/

c

 
@Cory5412 It's in response to his video.  He correctly typed "Boom! You're toast!" for the file to be burned, then the auto-correct changed it to "Boom! Your toast!"  He mentions in it in the video.  I was just sympathizing with his plight that is auto-correct.

 
Ah.

I haven't watched the video, so, that makes sense now.

With that in mind: "Boom! You're toast!" and "Boom! Your toast!" both have contexts in which they're correct, and if the watch in the video isn't in daily enough and/or this kind of phrasing isn't part of the normal wearer's writing on the device, then it likely didn't realize what the "correct" context was.

I've now realized that an entire generation of people who grew up texting shorthand and have no idea how to spell are now writing the source code to the operating system.


I think that "the kids can't write these days" is both outright wrong and a really bad mis-diagnosis of the goings-on at Apple and Microsoft. In my experience, people dropped T-9 "txt-speak" the literal instant they could, once touchscreen phones like the iPhone and keyboarded featurephones like the LG EnV and the like became available.

The other thing to realize is, the people in that group who had T9 phones as children or teenagers are basically in their 30s now. There's definitely informal shorthands that exist to this day, but let's be real: That's never been a tech thing and it's always been a young person thing. Plus, use of or knowledge of a shorthand doesn't necessarily mean someone has poor command of a "real" language. 

The other-other thing is that command of a programming language doesn't necessarily imply command of a human language, same with the reverse. They require different kinds of thinking and problem solving.

The other-other-other thing is that largely I think it's (as above) badly mis-diagnosing the problem with Apple (and Microsoft) to say that "kids these days" (who are probably the same age as you are) using shorthand in some contexts is what's causing problems with the OS.

It's been noted elsewhere but Catalina is a relatively big upheaval of a lot of long standing technologies (Which Apple has been telegraphing fairly clearly since 2002 that were eventually going to go away) and at the same time adds a bunch of user-facing features to the OS. The rest of the ecosystem (watchOS, tvOS, and iOS/iPadOS) are subject to what happens on the Mac because they all share the same core technologies.

Add to that, that Apple hasn't been breaking its release pace for several years and continues adding to the platform.

The only reason it works at all is likely because most of the core OS (kernel, etc.) is still based on legacy code from the 90s,
In my experience, at least on the Mac, things Apple doesn't care about have rotted BADLY and work way more poorly than they did ~5-10 years ago. Have you burned a CD/DVD/BD since 2010? Since El Cap or Sierra or so it's way worse than it used to be, especially if you like using disk images to get things ready. To add, Apple never added DMG templates for disc sizes provided by HD-DVD and Blu-Ray, even though those burners have been supported by the OS at least since 2009.

NFS is also broken in OS X and AFP has atrophied badly since the switch to Samba in 10.9 or so. Not to mention that Samba is still kind of weird in OS X. For example, to this very day in Catalina Apple warns you that enabling Samba for your account causes it to use a less secure password storage method. 

Apple deserves the criticism they receive about the OS, but we shouldn't be pinning it on kids who use shorthand when they're texting or IMing with their friends.

I could go on, but it'd be too political
Just as a heads up, by the time you've posted whatever made you think of this phrase, you're probably stepping on or over the line already.

 
With that in mind: "Boom! You're toast!" and "Boom! Your toast!" both have contexts in which they're correct, and if the watch in the video isn't in daily enough and/or this kind of phrasing isn't part of the normal wearer's writing on the device, then it likely didn't realize what the "correct" context was.
I'd be willing to grant you that one, it's probably difficult for analytical AI to grasp contextual ideas, but my iPhone is a daily driver and it constantly attempts to switch around "they're," "there're," "there," and "their," and "its" and "it's."  There're are clear grammatical and spelling rules for these implementations, it shouldn't be getting confused.  I have a hard time thinking of a context in which either a contraction or a possessive word is correct.

Just a pet peeve of mine is all.

 
I mean, this has been The Problem(TM) with computerized grammar and spelling checking since they started existing in, like, the 1960s or 70s as part of AT&T's UNIX-based publication systems.

I think AI might make it better, and room for more rules helps, but those will only get us so far.

The interesting thing about autocorrect is that it seems that Apple's extended it to consider more context now. I've seen my iPhone, new as part of iOS 13, correct further back in the sentence as more of it comes in. The other thing is, I wonder is if the learning gets reset between major iOS reinstalls. Apple's big push for privacy with its machine learning stuff means that most ML/AI is done on-device and it seems like getting that learning to translate person to person or even from one person's (say, iPod Touch) to their iPhone is something Apple's not good at yet. 

(And, arguably, getting each person to train their own devices makes sense, so person-to-person or aggregate ML about autocorrect might not be Good(TM).)

It also occurs to me that part of what was meant earlier was that the people programming ML for autocorrect and spelling checkers don't know how to spell, and that might be true, but I'm imagining in larger projects, the dictionaries are sourced elsewhere, or at least from different team members.

I.e. one person didn't sit down and write the algorithm for autocorrect and program all the rules into it in one sitting, or anything like that.

Unfortunately, on that front, thiese things mean that the way these tools get better is through use and generational iteration. An iOS6 device is probably as good as it will ever be, and autocorrect becoming better over the years is absolutely a real thing that happened, but also in my experience after a device rebuild or a major OS upgrade, autocorrect is annoying for a few weeks while it learns your preferences.

Overall, I'd say autocorrect saves me more time than it wastes so I leave it on, at least on my phone.

 
Back
Top