Because the main utility of Art is to be observed. The main utility of code is to be compiled into a piece of software.
Why shouldn’t I treat alignment with my values, the degree to which the code fostered a community that was pro-social, or the beauty of the code […]
I never said you shouldn’t. Just that it’s secondary to code’s functionality. Also, specifically in case of the Linux kernel, the community and its values stay the same. All that changed is a clause in the rules.
Again, and I brought up more details elsewhere in this thread. This is assuming utility as the principal axis. You highlighting art as having a utility "to be observed* is more of this neo-liberal hyper optimization psychology.
I am awash in projects that compile. Frankly, for most use cases, getting the code to compile is a pretty easy step. But all those other axis? Those are much tougher.
So, yes, “does it compile and run” is generally table stakes as I can’t interact much with the code without that step. However, comparing it to art, that is functionally the equivalent to “is it visible to a human somehow” as far as requirements to be considered art.
Because of this, the utility of code, that is “does it serve my needs”, is not the principal axis by which to judge it for me. It is just one of many axis’ that are used to judge.
This isn’t limited to code by the way. Every field, and every technology, gets this treatment. It is simply not enough to make a product that does a task. I’m looking for conviviality.
Because the main utility of Art is to be observed. The main utility of code is to be compiled into a piece of software.
I never said you shouldn’t. Just that it’s secondary to code’s functionality. Also, specifically in case of the Linux kernel, the community and its values stay the same. All that changed is a clause in the rules.
Again, and I brought up more details elsewhere in this thread. This is assuming utility as the principal axis. You highlighting art as having a utility "to be observed* is more of this neo-liberal hyper optimization psychology.
I am awash in projects that compile. Frankly, for most use cases, getting the code to compile is a pretty easy step. But all those other axis? Those are much tougher.
So, yes, “does it compile and run” is generally table stakes as I can’t interact much with the code without that step. However, comparing it to art, that is functionally the equivalent to “is it visible to a human somehow” as far as requirements to be considered art.
Because of this, the utility of code, that is “does it serve my needs”, is not the principal axis by which to judge it for me. It is just one of many axis’ that are used to judge.
This isn’t limited to code by the way. Every field, and every technology, gets this treatment. It is simply not enough to make a product that does a task. I’m looking for conviviality.