Re:One Way to Represent Things
by TeMPOraL on Thursday February 25, 2021 @09:29AM
(#26263087)
This connects to something I call "code bureaucracy" - in my experience working on legacy code, upwards of 50% of programming is being spent on shuffling data from one place to another, converting its type several times along the way, because different parts of the system - both internal and third party - each define their own version of same or similar types.
I wish in particular we could reduce the number of equivalent types across libraries, but I feel the solution will have to involve tagging types with WikiData identifiers or equivalent. So "Color" becomes defined as type Q1075, or perhaps Q1075<Q166194> to show you mean an RGB-denoted color...
I wish in particular we could reduce the number of equivalent types across libraries, but I feel the solution will have to involve tagging types with WikiData identifiers or equivalent. So "Color" becomes defined as type Q1075, or perhaps Q1075<Q166194> to show you mean an RGB-denoted color...