I play in a rock band, and as a consequence I’ve been spending a lot of time trying out audio software under linux. Usually when I’m trying out programs I have quite a high tolerance for bugs, clunkiness and bad designs, but when I’m using computers to record music I want to get on with the music and forget about the computers.
Without being disrepectful to the efforts of the Linux Audio Developers, currently linux ain’t a great place to be for audio. It’s getting a lot better with ALSA and Jack. But there’s no way I would recommend linux audio to anyone other than a hardcore techy.
So, should I install Windows and do audio there? I’d rather not give Microsoft any money. Maybe I should buy a Mac? I’m sure the grass would be greener over there. Certainly, the idea of paying some relatively small amount of money to get some better quality software sounds attractive. Gosh, that’s me .. a devout linux user .. wishing for a bit of commercial software.
There’s nothing special about these other operating systems in terms of the technical features they offer. The difference is the presence of commercial software companies who produce decent quality applications. You don’t get much of that under linux. These companies spend a while checking out user requirements, writing the code (including all the boring bits) and only shipping when it’s good enough to capture a reasonable share of the market. The end result is never going to be perfect bug-free software, but it’s pretty good.
I’d love there to be a top-class open source audio package for linux. But I don’t see how one is going to appear. If I were to write such an open source package, I’d have to do it in the evening after I come home from work. After all, I need to work during the day in order to buy food, pay the bills and live within our current economic system.
So, there’s the rub. If you want to get a team of focused developers working on an application, you need to pay them so that the project can be their “day job” and they can pay the bills. The only way you can pay them is if you can make money by selling the results of their efforts. Commercial software makes sense.
There’s certainly lots of people out there who expend huge effort developing open source software for apparently very little reward (the guy writing Ardour comes to mind). I would like to be able to do this kind of stuff without burning the candle at both ends. I work enough (paid) hours programming for my employer, and that leaves me disinclined to spend the remaining waking hours coding.
Also, since the volunteer brigade consists almost entirely of geeks, they have great success at certain types of application, such as web servers and compilers. Geeks like playing with new technology. They like doing the cool stuff, and consequently they tend to leave the boring bits of applications incomplete. Witness the number of projects with some small bit of “cool technology” at the core, but with atrocious GUIs. Maybe audio software is more left-brain touchy-feely and doesn’t win so big with the volunteers.
Apart from volunteers, there are other ways in which open source software gets built. Some open source software comes out of academic research projects, funded by government or industry. Some software starts life as an internal company tool which gets jettisoned, such as the Objective C support in gcc. A small amount of software is specifically commisioned by someone who pays a programmer to fulfil their requirements. I’ve done this kind of work before, but there’s not very much call for it.
Economies of scale make “commisioning” unsuitable as a method of seeing that good linux audio software get written. When a commercial company wants to build a new application, it takes on a certain amount of risk (the cost of development) which it hopes to recover through many sales of the product. The cost of the product is ultimately shared across many people. If someone were to commision an open source audio project they would singly bear the cost of development, which makes it prohibitively expensive.
I appreciate the technical advantages of open source software. I have often took advantage of the opportunities for learning, extending and fixing open source program which I couldn’t have done if I were using closed commercial software. And, I’ve volunteered lots of time to work on such projects. But I don’t see how it’s possible to truely walk the free-software walk when we live in a capitalist economy. RMS can believe that “reward is often not a motivator” if he wants, but peer recognition isn’t going to pay the bills.
Actually, I’ll postulate a thought experiment in which we already live in the RMS world, where all software was free. One day, someone comes up with this radical new notion of “proprietry software”. The promise of these crazy guys is that, if you’re prepared to loose some of your software freedoms and pay them a reasonable amount of money for results, they’ll be able to get some programmers together to concentrate full-time on the software, rather than working in a call-center or whatever they’re currently doing. What’s more, they’ll be able to get HCI experts to help design the GUI, and good authors to write the documentation.
So, my original question was “how do you write better applications?”. Open source may have many eyes making bugs shallow, but commercial software has fulltime eyes working on the program every day.