I don’t want this to read like a diss. You’re on a reasonable overall track of thinking here, in my view; I just have criticisms of the article as written. Perhaps it’s even a good article that will come up in a few years time as having been useful; hard to know ahead of time, reviewers are often just wrong.
But, it seems to me that the three basis vectors {space, time, information} in the concept space are not clearly justified, aren’t derived by construction in a way that makes them solid and useful concepts for me as a reader, and the writing is meandering; it’s writing like I write, combining interesting concepts and gesturing that there’s probably a formal grammar nearby that combines them in an even more interesting way. it doesn’t seem like your understanding level is that far below being what I’d call a useful crackpot, which is also approximately where I am with a lot of this stuff. The culture part might be what I’m having issue with, especially sacred geometry, but I think I recognized its influence far before that; eg, in the fact that you connect your three basis types to RGB with unclear justification. One way to put it is, sure, geometry is sacred and we’re made of it alright, but figuring out which geometry is sacred and why is the entire history of experimental and theoretical science; usually people who get excited about sacred geometry are connecting patterns overconfidently, with insufficient justification to warrant calling the connection a “proof”. Eg, information geometry, a very interesting field, involves weird shapes like the pseudosphere.
You also simply misused a lot of words at the beginning. Within the stuff that is actually legitimate, you’ve gathered interesting things in one place and gestured at the fact that symbolically manipulating them in the ways implied by an unspecified series of ?python-ish? functions could be cool. But the difference between pseudocode and code is precise specification. what, exactly, does compile_to_atoms to, after all? I can certainly come up with some very plausible things, but note that a python function can’t return atoms, only descriptions of them, which will then be simulated on one of many possible physical computers. You’re not totally barking up an invalid tree or anything and I don’t think your approach is unsalvageable, you’re right that there’s a lot of reasonable connection to see.
In general, approximate compression is what has been called “fake frameworks” on this site before; fake frameworks can be fine, I guess, but my preference is to recommend not overvaluing dimensionality reductions that turn out to not cut reality exactly. The interesting thing here is that it seems like it ought to be possible to understand perfectly, so giving up and settling for anything less than a true framework seems like a letdown to me.
That said, I think your post doesn’t warrant −20, so I’ve reversed my downvote into a strong upvote back to −10. I don’t think I’d upvote it past −5 as is with shaky grounding and type conversions. Fixing those type conversions to make them both elegant and understandable to more programmers is not a trivial request, and it’s not a totally useless post. But I wouldn’t recommend most folks on here read it.
I don’t want this to read like a diss. You’re on a reasonable overall track of thinking here, in my view; I just have criticisms of the article as written. Perhaps it’s even a good article that will come up in a few years time as having been useful; hard to know ahead of time, reviewers are often just wrong.
But, it seems to me that the three basis vectors {space, time, information} in the concept space are not clearly justified, aren’t derived by construction in a way that makes them solid and useful concepts for me as a reader, and the writing is meandering; it’s writing like I write, combining interesting concepts and gesturing that there’s probably a formal grammar nearby that combines them in an even more interesting way. it doesn’t seem like your understanding level is that far below being what I’d call a useful crackpot, which is also approximately where I am with a lot of this stuff. The culture part might be what I’m having issue with, especially sacred geometry, but I think I recognized its influence far before that; eg, in the fact that you connect your three basis types to RGB with unclear justification. One way to put it is, sure, geometry is sacred and we’re made of it alright, but figuring out which geometry is sacred and why is the entire history of experimental and theoretical science; usually people who get excited about sacred geometry are connecting patterns overconfidently, with insufficient justification to warrant calling the connection a “proof”. Eg, information geometry, a very interesting field, involves weird shapes like the pseudosphere.
You also simply misused a lot of words at the beginning. Within the stuff that is actually legitimate, you’ve gathered interesting things in one place and gestured at the fact that symbolically manipulating them in the ways implied by an unspecified series of ?python-ish? functions could be cool. But the difference between pseudocode and code is precise specification. what, exactly, does compile_to_atoms to, after all? I can certainly come up with some very plausible things, but note that a python function can’t return atoms, only descriptions of them, which will then be simulated on one of many possible physical computers. You’re not totally barking up an invalid tree or anything and I don’t think your approach is unsalvageable, you’re right that there’s a lot of reasonable connection to see.
In general, approximate compression is what has been called “fake frameworks” on this site before; fake frameworks can be fine, I guess, but my preference is to recommend not overvaluing dimensionality reductions that turn out to not cut reality exactly. The interesting thing here is that it seems like it ought to be possible to understand perfectly, so giving up and settling for anything less than a true framework seems like a letdown to me.
That said, I think your post doesn’t warrant −20, so I’ve reversed my downvote into a strong upvote back to −10. I don’t think I’d upvote it past −5 as is with shaky grounding and type conversions. Fixing those type conversions to make them both elegant and understandable to more programmers is not a trivial request, and it’s not a totally useless post. But I wouldn’t recommend most folks on here read it.