Yes but that doesn’t mean they’re not important in ensuring there isn’t a messaging monopoly.
Obviously in an ideal world we’d have multiple interconnected secure apps with some cross-platform interoperability, but until then I’ll settle for one government/corporation not having all of everyone’s private conversations.
Lots of people want adjacent room lights or beyond to be on.
I turn all the lights in my house on at night, despite the savings loss, because I just prefer being able to see into other rooms. (I also use 100w-equivalent bulbs, to really boost the brightness).
Some people have fears, rational or irrational, about the dark. Children, people paranoid about someone breaking in, etc.
Some people feel pets should be able to see where they’re going.
So, most windows installations come with an OEM key because it came pre-installed. OEM keys, last I knew, don’t have this support, because the manufacturer is responsible for that.
If you bought a lenovo laptop, its on lenovo.
But anyone has been able to buy windows directly with a standard license key and windows supports those computers directly. I’ve never bothered to use it but I worked with people who did and (again, last I knew, some 10+ years ago) they got someone with a thick accent reading from some support article who didn’t know what they were about.
But they could call. Technically that’s support.
I do agree it’s not realistic, but it can be done.
I have to assume the people that allow the AI to generate 10,000 answers expect that to be useful in some way, and am extrapolating on what basis they might have for that.
Unit tests would be it. QA can have a big back and forth with programming, usually. Unlike that, QA can just throw away a failed solution in this case, with no need to iterate on that case.
I mean, consider the quality of AI-generated answers. Most will fail with the most basic QA tools, reducing 10,000 to hundreds, maybe even just dozens of potential successes. While the QA phase becomes more extensive afterwards, its feasible.
All we need is… Oh right, several dedicated nuclear reactors.
The overall plan is ridiculous, overengineered, and solved by just hiring a developer or 2, but someone testing a bunch of submissions that are all wrong in different ways is in fact already in the skill set of people teaching computer science in college.
Well actually there’s ways to automate quality assurance.
If a programmer reasonably knew that one of these 10,000 files was the “correct” code, they could pull out quality assurance tests and find that code pretty dang easily, all things considered.
Those tests would eliminate most of the 9,999 wrong ones, and then the QA person could look through the remaining ones by hand. Like a capcha for programming code.
The power usage still makes this a ridiculous solution.
I used to work as tech support and can say that there isn’t.
For instance, in some Asian countries the shutter sound is legally mandated. Apple accomplished this by checking where you are. If the phone’s region is one of those areas, It’ll always make a shutter sound. If your region wasn’t one of those areas, and the phone could still tell it was in the area (like a UK phone taken on vacation) It’ll make the sound while it was there.
There’s a bunch of ways to implement that, but the employee-facing article detailing this feature specified that a user who was from one of those countries but moved here could factory restore the phone to get it unregulated again.it had employees who were asked to do that to verify they weren’t in the original country anymore as a “cover your ass” legal disclaimer kind of thing.
This was multiple iPhone generations ago, now, but I doubt they’ve changed. Economies of scale say having one process is easier.