 | This article is rated Stub-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||
| ||||||||||||||||||
Data as code redirects here. It contained an article in the past, which has been moved to Draft:Data as code. Diego ( talk) 16:12, 10 January 2014 (UTC)
I copy here the references, as they could be used for a WP:BROADCONCEPT article. Diego ( talk) 13:29, 16 September 2014 (UTC)
- Propylon — CTO Articles v Code is data, and data is code
- Bill de hÓra: Execute this: managing configuration in programming languages
- The DNA of Information
- Atoms and bits
- Customhouse c Bits and Atoms
I read the 2024 paper and it is quite different from the Lisp concept of "code as data", I don't think it can be part of the same article. Per the paper, DaC is "the idea that a single entity is responsible for the generation, storage and interface of data." This entity manages the format of the data, meta-data, documentation, and caching of generated data. In contrast, in Lisp, "code as data" is some basic stuff about manipulating ASTs in macros - there is no caching, no documentation, and no hidden format. I guess the point of some of these sources is that the distinction between code and data is irrelevant, but I would say maybe it is not so simple and we should split the article into two, "code as data" and "data as code". Mathnerd314159 ( talk) 17:34, 1 March 2024 (UTC)
- Also per WP:NCCAPS, the second article would be Data as code not Data as Code. For example, see Infrastructure as code. Mathnerd314159 ( talk) 17:53, 1 March 2024 (UTC)
|
| This article is rated Stub-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||
| ||||||||||||||||||
Data as code redirects here. It contained an article in the past, which has been moved to Draft:Data as code. Diego ( talk) 16:12, 10 January 2014 (UTC)
I copy here the references, as they could be used for a WP:BROADCONCEPT article. Diego ( talk) 13:29, 16 September 2014 (UTC)
- Propylon — CTO Articles v Code is data, and data is code
- Bill de hÓra: Execute this: managing configuration in programming languages
- The DNA of Information
- Atoms and bits
- Customhouse c Bits and Atoms
I read the 2024 paper and it is quite different from the Lisp concept of "code as data", I don't think it can be part of the same article. Per the paper, DaC is "the idea that a single entity is responsible for the generation, storage and interface of data." This entity manages the format of the data, meta-data, documentation, and caching of generated data. In contrast, in Lisp, "code as data" is some basic stuff about manipulating ASTs in macros - there is no caching, no documentation, and no hidden format. I guess the point of some of these sources is that the distinction between code and data is irrelevant, but I would say maybe it is not so simple and we should split the article into two, "code as data" and "data as code". Mathnerd314159 ( talk) 17:34, 1 March 2024 (UTC)
- Also per WP:NCCAPS, the second article would be Data as code not Data as Code. For example, see Infrastructure as code. Mathnerd314159 ( talk) 17:53, 1 March 2024 (UTC)