[CodeGroyper]

It works well for computer science as well. Values have types (forms) and bytes (matter). One type can be instantiated in multiple ways, for example you can have multiple integers, like 1,2,3,4 or the bytes 01000001 can represent different information, like 65 or 'A'.

The interesting thing is null, because here the distinction sort of breaks down.

[Vektorceraptor]

But that's not entirely true, because the mapping alone doesn't give you any ordering relation or comparison options. Translating the natural numbers into bytes doesn't tell you how they should be ordered. We determine the 'form' of the order with our minds.

[MontagFTB]

Could the sort be another form? Taking the article’s example, I could sort a bunch of tables by height or weight or some other attribute. That sort order then takes on a form that was not there prior to the sort. To think of it another way, after the tables (or values in CS) are sorted, the sort has been “assembled”.

[Vektorceraptor]

I don't think so. Height and weight are sorted/ordered numerical, and numerals are not properties of the table, nor of its weight or height. The form of the relation is abstract, it's actually between the values attached and not the objects, and therefore in our mind.

[MontagFTB]

I wonder if this is the reason Hylo was given its name: https://www.hylo-lang.org/

[capableweb]

> The interesting thing is null, because here the distinction sort of breaks down.

Kind of like zero, represents "nothing" but also "something", at the same time.