As I heard it explained, the original manuscript had the humans kept alive because the Matrix was actually running on the humans' brains as the computing substrate. This both made much more sense than humans as a power source, was more horrific, and a better story.
Apparently this was deemed to hard for the unwashed masses to understand, and we were left with this battery analogy instead.
Huh interesting. It makes also much more sense then to have some humans have the ability to change things in the Matrix, considering it was basically running on their brains.
The big question in that case though is why? Why would the AIs keep a simulation of the old world?
To answer your Q tho, this was in one of the sequels I believe, basically the first iterations of the matrix were like "Eden" but humans couldn't adapt to it so they redesigned and iterated it into what you see in the movie. The idea being that if humans weren't busy they'd realize they were enslaved so they had to make a system to keep humans occupied and stimulated enough to be useful.
> Kind of like vegans who haven’t tasted dairy for 10 years tend not to be reliable judges of the quality of vegan mayo - how could they possibly know?
Wait, how is mayo, vegan or not, related to dairy?
Dairy is a category that depending on context may or may not include eggs. In this case the distinction doesn’t matter. Vegans wouldn’t have experience with strictly defined dairy or eggs.
For some reason, people lump eggs in with dairy, presumably because they're unaware of the difference between hens and cows. You'd have to have quite a lot of detectable THC in your system to confuse the two, but here we are, people think that eggs are the same as milk.
To be fair, my milkman delivers eggs as well as milk, cream, and butter, but they come from a totally different farm.
This is not surprising at all, to me. Just commit the example input and write your test cases against that. In a nicely structured solution, this works beautifully with example style tests, like python or rust doctests, or even running jsdoc @example stanzas as tests with e.g. the @linus/testy module.
The example input(s) is part of the "text", and so committing it is also not allowed. I guess I could craft my own example inputs and commit those, but that exceed the level of effort I am willing to expend trying to publish repository no one will likely ever read. :)
It's definitely ai slop. See also the nonsensical attempt to conditionally load SQLite twice, in the dynamic imports example.
The list of features is nice, I suppose, for those who aren't keeping up with new releases, but IMO, if you're working with node and js professionally, you should know about most, if not all of these features.
I've visited Lady Musgrave Island in the Great Barrier Reef. It is covered with trees called "the grand devil's-claws", the seeds of which are barbed and sticky. The seeds stick to the wings of birds eating seeds, and so they can spread across islands.
However, a visitor to the island will soon notice lots of dead birds on the ground. There are no predators or scavengers, so the birds lay there decomposing.
Thus, the trees use the birds not only for reproduction, but also for food. It's a carnivorous forest out there on the reef.
Apparently this was deemed to hard for the unwashed masses to understand, and we were left with this battery analogy instead.
reply