Yeah but that’s art. Code is very much a means to an end. Code can be artistic i suppose but it does actually have to do something at the end of the day. And if it works it works.
Definitely agree with a lot of that. Indeed in this era of abundance why do we need to squeeze more and more out of everything.
However computing has been one of the most valuable inventions of all time. A script is usually written to automate a process. If the script doesn’t work, it’s useless. Not all disciplines are the same. The value of the code is what it does.
You can certainly talk about the horrors of AI under capitalism but i don’t think open source developers should have to think about it. I’d rather they make software better for everyone than get tied up thinking about how to solve the impossible.
In the universe where the “where it came from” can’t affect the end quality, the question itself indeed becomes irrelevant. And in case of the Linux kernel it is indeed irrelevant, as the code will be reviewed, appraised and tested before releasing.
And yes, the utilitary mindset is more applicable towards code than it is to art. Unless we’re talking about stuff like ioccc, where the code itself is the form of art, code is just a mean, not the end.
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.
You see, it is the principled axis though. Let me paint an analogy: suppose, you’re very thirsty, but there’s no water to be found. You see chips, dried fruit, cakes, biscuits, but no water. Would you really care about how ethically all of those were sourced, how nice they are, or how much the cook loved to make them? If someone started to tell you all of this snacks’n’deserts lore while you were literally dying of thirst, you’d most probably become very irritated, because all of those beautiful snacks and desserts is not what you need right now. What you need is water, and hour by hour you’re starting to care less and less about how muddy it should be, or where it comes from.
What I’m saying is, when a certain niche is overflowing with various pieces, it might seem like utility is not primary, but the opposite becomes really apparent as soon as there’s nothing to fill in that said niche. The rest is just a privilege that we all have, thanks to the abundance of literally everything that we live in. I too have the privilege to avoid projects written in Python, simply because i have a personal preference against it, or to avoid shady vibe-coded slop. With linux kernel tho? I mean, if someone clones it, and does a better job at not letting bugs into production, while releasing at the same pace or quicker than the current kernel project does, i’ll switch to it too. Except i doubt somebody could compete with a team of seasoned vets, that know how to use their tools and can with ~95% accuracy tell which parts of code would break at a first glance. Until then, i’ll stay on vanilla linux kernel, because it does its job of keeping my pc functional, which i need to win some bread.
My entire argument is that value is judged against a wide host of different axis.
And you continue to fail to see that I have never said otherwise. There is a certain logical leap between “this is the only factor that matters” and “this is objectively the main factor, but we have the luxury to not care about it because we live in a post-scarcity environment”. You can afford to not choose the croissant because you know there’s other food to choose from, and more over, that there are other croissants just like this one, but with no child labor inside.
On to your main point as to the value of non-utility features […]
There’s no such thing as “non-utility feature”. But there’s the order of importance of factors, which is, of course, subjective and highly-cotextual. If you personally value the fact that a given software was written without the use of LLMs, than its functionality, because you somehow deem it as “more moral”, you’re free to stay on the outdated kernel, or switch over to NetBSD. I guess that’s the part of our discussion where you explain to me why you think using LLMs in an opensource non-profit collaborative project with the given rule that the person who submits the code is still fully responsible for it and should be able to answer any technical question regarding it is wrong.
deleted by creator
Yeah but that’s art. Code is very much a means to an end. Code can be artistic i suppose but it does actually have to do something at the end of the day. And if it works it works.
deleted by creator
Definitely agree with a lot of that. Indeed in this era of abundance why do we need to squeeze more and more out of everything.
However computing has been one of the most valuable inventions of all time. A script is usually written to automate a process. If the script doesn’t work, it’s useless. Not all disciplines are the same. The value of the code is what it does.
You can certainly talk about the horrors of AI under capitalism but i don’t think open source developers should have to think about it. I’d rather they make software better for everyone than get tied up thinking about how to solve the impossible.
That is so incredibly wrong that I don’t know where to even begin. Yes, they should think about it. We all should.
Open source developers do not have the power to enact change. AI needs regulation which must come from governments.
What a lame excuse for complicity.
deleted by creator
What code does is the least intetesting part of it for you?
Idk, AI use doesn’t automatically make something slop just like writing by hand doesn’t automatically make it good.
deleted by creator
In the universe where the “where it came from” can’t affect the end quality, the question itself indeed becomes irrelevant. And in case of the Linux kernel it is indeed irrelevant, as the code will be reviewed, appraised and tested before releasing.
And yes, the utilitary mindset is more applicable towards code than it is to art. Unless we’re talking about stuff like ioccc, where the code itself is the form of art, code is just a mean, not the end.
deleted by creator
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.
deleted by creator
You see, it is the principled axis though. Let me paint an analogy: suppose, you’re very thirsty, but there’s no water to be found. You see chips, dried fruit, cakes, biscuits, but no water. Would you really care about how ethically all of those were sourced, how nice they are, or how much the cook loved to make them? If someone started to tell you all of this snacks’n’deserts lore while you were literally dying of thirst, you’d most probably become very irritated, because all of those beautiful snacks and desserts is not what you need right now. What you need is water, and hour by hour you’re starting to care less and less about how muddy it should be, or where it comes from.
What I’m saying is, when a certain niche is overflowing with various pieces, it might seem like utility is not primary, but the opposite becomes really apparent as soon as there’s nothing to fill in that said niche. The rest is just a privilege that we all have, thanks to the abundance of literally everything that we live in. I too have the privilege to avoid projects written in Python, simply because i have a personal preference against it, or to avoid shady vibe-coded slop. With linux kernel tho? I mean, if someone clones it, and does a better job at not letting bugs into production, while releasing at the same pace or quicker than the current kernel project does, i’ll switch to it too. Except i doubt somebody could compete with a team of seasoned vets, that know how to use their tools and can with ~95% accuracy tell which parts of code would break at a first glance. Until then, i’ll stay on vanilla linux kernel, because it does its job of keeping my pc functional, which i need to win some bread.
deleted by creator
And you continue to fail to see that I have never said otherwise. There is a certain logical leap between “this is the only factor that matters” and “this is objectively the main factor, but we have the luxury to not care about it because we live in a post-scarcity environment”. You can afford to not choose the croissant because you know there’s other food to choose from, and more over, that there are other croissants just like this one, but with no child labor inside.
There’s no such thing as “non-utility feature”. But there’s the order of importance of factors, which is, of course, subjective and highly-cotextual. If you personally value the fact that a given software was written without the use of LLMs, than its functionality, because you somehow deem it as “more moral”, you’re free to stay on the outdated kernel, or switch over to NetBSD. I guess that’s the part of our discussion where you explain to me why you think using LLMs in an opensource non-profit collaborative project with the given rule that the person who submits the code is still fully responsible for it and should be able to answer any technical question regarding it is wrong.
deleted by creator