>>These are the two broad methods humans have for moving things around: pipes and buckets.
Interesting, but this list is somewhat incomplete. Two other methods of "moving things around" not covered in these stated categories include a.) Projectiles, and b.) Teleportation.
The latter is still in it's infancy. While the former may invoke thoughts of missiles and bullets from guns, really it's any matter/energy that is transmitted using energy without a container (i.e. clouds transmit water, antennas transmit radio waves, etc.).
>>Setting aside the complexities of time and identity for a moment, every fact must be three-dimensional, the smallest possible unit of information. [Article cit. 3 & 4] A three-dimensional fact might be represented as a proposition, a triple, or an attribute assigned to an entity. These are equivalent.
I had trouble with the statement that "facts must have three dimensions," so I checked the citations only to find zero reference to this '3D fact' assertion or what that actually is supposed to mean.
If someone can verify and support this assertion, or an example, please let me know. The post appears interesting, but I can't read any further without knowing that the basis of what follows stands on solid footing. The missing categories of "transporting things" leads me to believe that this paper is documenting an incomplete thought.Reply
> Facts aren’t physical things
Not true. Facts/information/data doesn’t exist without being represented in the physical world. When you tell somebody a fact, you are taking facts/information/data physically stored in your brain, copying it to a new physical medium (sound waves), and then again copying it to a new physical medium (the other persons brain). What is unique about facts/information/data is that it can be stored/represented in an almost infinite number of ways and that we can copy it from one physical state to another. However it doesn’t exist outside of the physical world. You can’t even think about this without using your physical neutrons to store what you are thinking about.Reply
> We do not mean function calls, callbacks, event loops, or other forms of method dispatch.
Those are all events that you might need to keep track of in some contexts (editors for example or debuggers). So there is nothing that will never be represented as events. The fact that somebody issued a command is an event that you might need to keep track of in some systems. An example is fraud or security pattern matching. In other words, an event is anything that has happened that you need to keep track of. It can be the fact that a single bit has changed, all the way up to high level system wide events. It all (as per usual) depends on your specific context and business requirements. So any attempt to nail down what is an event and what isn’t independently of context is a waste of time. A key press might be an event we care about in one context and not at all in another.Reply