Difference between revisions of "Materializable programs"
(→Related: added a few internal links) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 19: | Line 19: | ||
* [[Digital control over matter]] | * [[Digital control over matter]] | ||
* [[Digital matter]] | * [[Digital matter]] | ||
| − | * [[Programmable matter]] | + | * [[Programmable matter]] == [[Programmable materials]] |
| + | ---- | ||
| + | * [[Programming languages]] | ||
| + | * [[Programmatic 3D modeling]] | ||
---- | ---- | ||
* [[Deveuser]] | * [[Deveuser]] | ||
| + | ---- | ||
| + | * [[General software issues]] | ||
| + | * [[Software]] | ||
[[Category:Programming]] | [[Category:Programming]] | ||
[[Category:Software]] | [[Category:Software]] | ||
Latest revision as of 15:39, 18 August 2024
Materializable programs or materialized programs for the ones deployed and active.
At first glance this name does not seem to make much sense.
A program as in the sense of "the program code" can't really be materialized beyond a printout. Right?
A programs output can only be materialized (via some sort of decompression chain).
But what if the concept of live coding and micro-granular hot plugging gets
transferred over to programmatic control over technological artifacts?
Where any change in code directly and instantly transfers over to a change in physical state.
Where any change in the artifact directly and instantly transfers over to a change in the code.
Where the technological artifact is a projectional editing interface for the code allowing for direct manipulation.
Then the the name "materializable programs" (or "materialized programs" for the ones active and physically deployed) starts to make much more sense.
