I attempted to open the resulting full gif using GIMP to see all the individual layers but unfortunately it crashes about 12000 frames into the loading process.
This has zero canon justification, but I saw a theory on Reddit suggesting that the "Hero Defeated" ending of OoT was the natural result, but Link's wish on the Triforce at the end of LttP changed history to allow Link to defeat Ganon in OoT, creating the two victorious timelines in that game. It was a neat idea.
We run into that a lot using Mulesoft. 3 layer APIs, and each layer will discard error messages returned by the underlying layers unless we do tedious custom error handling. Makes it impossible for the teams using our integrations to know what they're doing wrong.
I occasionally use graphviz and pretty much always wind up frustrated with it. The syntax is pedantic and the resulting output is pretty ugly for all but the simplest graphs.
What's your use case for it? For manual diagrams, making an explanatory diagram for a presentation or something I would never recommend it. Declaratively typing out all your information is going to take just as long as setting it directly in drawio, but with less control over the result.
Where graphviz/dot has always shined for me is you have some application built around a data flow graph and occasionally need to debug a run with 50+ nodes at a time. So you write a file dumper for your structure. A visual makes understanding the structure so much faster, and nothing else seems to produce layouts nearly as good as dot.
For me, I sort of imagine the sensation of eating something and observe how I react to it. If it's a strong positive reaction, that's what I'm in the mood for. Otherwise, if it's kind of a more bored reaction, I cast my mind out for another idea and try again.
I would say taste and touch are my strongest recall senses. I can still remember the experience of my favorite sandwich at a local sandwich shop, discontinued around 2009.
For the apple test, while I can visualize the image of one, it's much easier to imagine the sensations associated with biting into one. The taste, the texture against my teeth, the stickiness of the juices, etc.
We're being forced to use some AI features in our IDE at work these days, and we see it make stuff up all the time. Very unpleasant to work with. It will tell us implementing something a certain way is impossible, when I've implemented it myself that way in the past. It will fabricate reasons why builds are failing. It will make assumptions about database schemas from thin air.
It's like a science fiction writer or an improv actor doing technobabble. If by chance it knows the actual answer it might use it, but even if not it still has to say _something_ that sounds plausible to a layperson. It'll never say it doesn't actually know, because their character it's acting as _should_ know.
reply