I’m guessing they adjusted the activations of certain edges within the hidden layers during forward propagation in a manner that resembles the difference in activation between two concepts, in order to make the “diff” seem to show up magically within the forward prop pass. Then the test is to see how the output responds to this forced “injected thought.”
It's one thing to wish that apps would put their data anywhere except dumping it in your home dir, but this is exactly why I hate the XDG spec. I want all data for a program--be it the configuration or the cache or the binary itself--to be in a single directory such that 1) "uninstalling" the program, completely and in isolation, is nothing more than just deleting that single directory, and 2) any program not doing arbitrary file I/O can entirely function while having access to only its installation directory, and nothing else on the filesystem.
This approach couples together everything though, in such a way there's no standard manner of wiping cache but not your app, configuration, etc.
XDG may not be perfect but wiping related data for apps following it is straightforward. There are a few directories to delete instead of 1, but still consistently structured at least.
I ended up going the opposite direction. My 11th grade trigonometry teacher forced me to repeat trig despite my having gotten a B. I was angry at the time! She did me a favor because by the time I got to Calculus in University it was very intuitive and I didn’t have much of a problem with it.
I went looking for mentions of Semantic Networks, RDF, triplets, taxonomy, or other common knowledge-related terms but I found nothing. Thoughts about pre-existing knowledge graph systems and how they may or may not apply to System? Thanks!
Obligatory C++ comparison: C++ has constexpr since C++11 and constinit since C++20. They mean more or less the same when applied to variables ("must be evaluated at compile-time"), but constinit does not imply constness.
D evaluates until it hits something it can't manipulate at compile time whereas constexpr requires things to be annotated as such, so the difference is slightly more subtle.
reply