There is an art to building software, no doubt, in terms of it being a craft. But I think you've misspoken about functional things being artistically beautiful. What you really should mean is that functional things can be aesthetically beautiful, which is true and different.
Art is primarily defined by expression and exploration, particularly revolving around human emotions. Software products, in the end, do not fit this category. There is a vast difference.
Edit: I defined it elsewhere a bit smoother. I define art as the exploration of emotional expression. Art products are the end result of that exploration. Live acts or art or performances could be viewed as a sort of merger between the two, either as a reenactment of the exploration or as a new exploration happening in the moment.
Software can be art in itself. Consider quines [1]. (Programs that, when run, produce themselves) They serve no real world purpose, and I consider them beautiful. Kind of like the restrictive format of a haiku. (Edit: Or perhaps tesselations, e.g. Escher's work [3])
I particularly enjoy what this artist(?) has done with their 128 language uroborus quine. [2]
Edit 2: I expect the objection will be that this is not functional, or a "product", however the uroboros quine does have practical uses. E.g. as a system stress test. If it were marketed as a stress test, its artistic value would still be apparent to a programmer examining its structure.
The statement of saying someone else's view of art is objectively incorrect or silly is in itself silly. I like your proposed definition of art, but as you know everyone is free to have their own conceptions.
I can agree with that to a degree. Of course, the gut reaction to any statement is typically the more emotional one. :)
However, I find that they didn't really make a statement about how they view art, although elaboration would help. I think people are confusing things being artistic versus being aesthetic. When people say "code absolutely can be art", I find it's too generic that it does indeed become a silly statement. It dilutes what art is and is overly biased to code, especially since it's likely to be coming from a software developer.
What I really think someone means by "code can be art" is that "code can be aesthetically pleasing", the latter of which I agree with. There's also a difference between "<some thing> as an art" as in doing the thing can be an art or craft and also calling the thing art.
The 80s underground scene had many zines that were programs.. the art would be part content part reader/application. The best part were the crazy menus.
The problem now is an application must look like all other applications or you would see more creativity. Making parts of the app 60% visible so the background came through had a cool visual effect.
Can you elaborate on what you're referring to or talking about?
Of course there are loads of software that people use in art. But in the end, those are still solving a problem and are not art. Examples are TouchDesigner, Processing, Logic, Studio One, Pure Data, vvvv, and much more. These software products are not art themselves but are rather solutions to problems to allow artists to create art easier. They are not art products, in my opinion, since they aren't the result of an exploration of expression.
Where the line is blurred for me is in live coding artistic performances. The software there is considered part of the art, as part of the performance. But even then, the software is a tool. If a person uses a hammer in a live art piece, is the hammer now suddenly art? No, I wouldn't think so. It's a tool serving as a utility or maybe medium. It isn't art itself. The art is the performance.
Of course there are always exceptions which cannot be captured in every argument. Something that blurs the line is something like DIN . But see, in such a software product, we begin to see expression and not just a thing solving a problem or being a tool. Similarly with Orca (although I wish they would change the name so as to not interfere with actual orcas which some populations are in danger of going extinct).
A tremendously important example is videogames which as well as being a multi-billion dollar industry akin to music are also a major medium of individual self expression.
In the broader set you have interactive fiction and a whole slew of art that shares a lot in common with time-based art. Demoscene is a good example of the latter.
Games certainly can be art! But I don't see how that conflicts with what I said or serves as a counterexample. Games are not just software products. They are the culmination of work by artists, designers, writers, and engineers. The end product is often an artistic piece, and a rather interesting one. Games being art doesn't suddenly mean software products are art. The software itself helps drive the art but is not the art itself. I feel a good way to think about it is that software and code running the game is not art in the same way that the paint in a painting is not art.
My favorite game designer is Fumito Ueda. His games of Ico, Shadow of the Colossus, and The Last Guardian are prime examples of games can be art.
Videogames are software products though so are a prime example of software products that are art. To quote your own recent definition of software:
"I have always viewed hard, firm, and soft as a description of the ware's malleability. Hardware is not easily changed or updateable, if at all. Firmware is typically code deployed to stay in hardware like an EEPROM, flash, or FPGA, where it can be changed but not necessarily dynamically or easily. Software is able to be easily molded and changed."
And whilst videogames do require traditional artists so do the construction of other mundane software products. Also invoking other disciplines rather ignores a lot of the work that goes into the gameplay itself which is entirely software driven.
Not to mention the other examples you studiously avoided.
> Videogames are software products though so are a prime example of software products that are art.
Did you think about or read what I described? Because I specifically addressed how I think video games being art does not make software products and code art. You aren't elaborating and then just restating an opinion I've already discussed.
If video games being art means that software products and/or code is art, then you need to consider that the material (paint, metal, etc.) used in paintings and sculptures is art as well and all the other repercussions of such a conclusion. No one would argue that. The paint in paintings is part of the medium and brushes and other such things are part of the tools of the process. In the case of video games, the software is a kind of both tool and medium of how that art is created and experienced. No one is saying software can't be a medium for art, but it isn't the art itself. And again, like I've already said, I don't think video games can simply be defined as software products. Other things called software products, like mobile apps, also have artists and designers, but there the situation is even more removed from art because the app is not expressing anything but is rather solving a problem, providing a service, or giving functionality.
> To quote your own recent definition of software
That quote has nothing to do with this discussion, so I'm not really sure why you're pulling it here. It was from a completely different post, and a non-native English speaker had remarked about how they had thought that the firm in firmware meant something else. I wasn't defining software but rather discussing how hard, firm, and soft in hardware, firmware, and software could be thought of.
> Not to mention the other examples you studiously avoided.
I didn't avoid anything. I didn't feel I had anything to say that adds to the discussion without repeating what I already said. Yes, they're examples. And?
I didn't say that. And just repeatedly stating something doesn't make it true, especially if others disagree and you refuse to elaborate, discuss, or explain.
Plus the implication that music might not be a tool for a specific purpose (which it is also absolutely in some contexts).
The thing is that "music", is not "one thing". It all depends on the purpose, if there is one, and on the intention of the composer and of the players and of the audience.
Here, Spotify's CEO adresses a very specific market in the music industry, not "musicians" per se.
This is a tired argument that lacks much nuance.
Ill believe this when people regularly gather in the thousands to see a brilliant coder at work or view amazing code in a gallery.
Are there not thousands of conferences each year? People giving talks at meet-ups, the yearly Apple developer conference draws thousands of people. All events that people sign up for voluntarily to listen to someone else talk about code.
As for viewing it; there are also many places where people participate in coding competitions or code golfs, where others judge and appreciate the code.
Is that really so different from going to a concert or an art gallery?
