Except that the word, "recall", doesn't have two different meanings. It literally means the same thing here as it does for a recall wherein a Jeep has to have its shifter replaced / tweaked / whatever.
Just so happens that the latter can't be fixed via software, because it's not a software-based safety failure.
The former is fixable via software update, because it is a software-based safety failure.
Both, however, are safety failures. Both need to be fixed. Both situations incurred regulatory requirements to notify customers and provide a timely fix at no cost to affected customers, whether within or without the vehicle's warranty.
In short: both are recalls, and recall means the same thing in both cases: notify, fix, or face regulatory consequences.
I too enjoy putting "quotes" around a word to make it seem like it means the thing I want to pretend it means, instead of engaging honestly with the actual situation. :-)
It should when it's required by the NHTSA and comes along with mandatory reporting, notification, and deadline obligations, along with optional free on-site execution of the fix.
That's what makes it a recall. A software update is the mechanism, the recall is the "Tesla did something wrong and is being held accountable" part.
I think you make a good point, benchmarks and metrics are indeed a better proxy for performance. Seems worth pointing out that, while "nowhere near half in [your] experience" are completely wrong, I don't take your word for it either. :-)
The trouble in my view is that the only way to know that the answers you're getting are accurate and not misleading is to study up on the answers elsewhere - which is a great habit to nurture, but is also precisely why these tools tend toward uselessness in their "general AI" bids. If I can't know how the answer was built, or how good that answer is, there's no point asking it - I'll just do my own reading and apply appropriate discernment as I go.
To be fair, hardly anyone does this today, nor did they before LLM-based chat bots... So it's a moot point, because society is largely doomed anyway. But a moot point can still be a valid one.
I also think the author makes a good point that we frequently confuse performance for competence. "It does a really good job at <X>!... or at least does a damn fine job of mimicking someone who acts like they do a really good job at <X>!"
By way of analogy, consider Elon Musk - by all appearances, he's a genius and is saving humanity - but by dint of his narcissism and largely smooth-brained approach to... well... everything... he's running all of us into an earlier planet-size grave than is necessary. His performance is fantastic, his competence is nonexistent.
Heh definitely an eyebrow-raising comment!
On a second read of it though, I took it more as "because minimizing the code written is a pattern observed in the wild, AlphaCode mimics it as that's what it learned from."
>> In the case of Wayland, the “vague authority” are a bunch of volunteers who have devoted tens of thousands of hours of their free time towards making free shit for you.
>That does not mean anyone is under an obligation to like it.
Doesn't seem that was the point of that statement. Rather, it's asserting that it's invalid to claim that the very people who built the thing in the first place are a "vague authority".
How true the accusation it, I dunno, but that's my read of the sentence - not that the volunteer devs are somehow entitled to endearment by virtue of their volunteering. :-)
Just so happens that the latter can't be fixed via software, because it's not a software-based safety failure.
The former is fixable via software update, because it is a software-based safety failure.
Both, however, are safety failures. Both need to be fixed. Both situations incurred regulatory requirements to notify customers and provide a timely fix at no cost to affected customers, whether within or without the vehicle's warranty.
In short: both are recalls, and recall means the same thing in both cases: notify, fix, or face regulatory consequences.