How To Make Money With Free Software
fons writes "Dutch Python hacker/artist Stani took part in a contest organised by the Dutch Ministry Of Finance to design a 5 euro commemorative coin. And he won, using only free software: 'The whole design was done for 100% with free software. The biggest part consists of custom software in Python, of course within the SPE editor. For the visual power I used PIL and pyCairo. From time to time also Gimp, Inkscape and Phatch helped quite a bit. All the developing and processing was done on GNU/Linux machines which were running Ubuntu/Debian. I would have loved to release the coin under the GPL, which could maybe solve the financial crisis. However for obvious reasons I was not allowed to do that.'"
Or the purpose of the article is to bring light to the fact that he won the contest using only FOSS software, and they chose the title of "How to Make Money" as a pun, where you would assume they meant "how to profit", but they literally meant "how to design money".
By what name do you wish to be mourned?
This guy won due to superior design, not due to the fact that he used free software. The free software is in the background, contributing but almost incidental to the final product. That's how is should be though. Free software released the artist from the constraints of having to fit in with someone else's idea of what software or technology he should be allowed to use, leaving him free to be creative and follow his own unique path.
...it made me giggle with joy to see the guy mention he won against people using Adobe products. I teach Adobe products to impressionable college students, and when they sign up to take my class and purchase their own copy of Photoshop or Illustrator, boy do they think they have ARRIVED in cool-town. Many of my new students think that once they *understand* how to use Photoshop better than most, they are now a graphic designer, creative person, illustrator, web designer, etc.
So I started doing an extra credit assignment where I tell them they are not allowed to use Adobe products, and they have to design a postcard. They use any package they want; most use GIMP or Inkscape because they're free. Without fail, they come back and say, "hey, I can't do anything with this. It's not Adobe. It sucks." So I point out to them that their Adobe software skills make them think they're pretty good at design. But what happened to their awesome design skills when they started using another software package? Does the software really suck, or do they just hate it because of its non-Adobeness? I show them nicely-done work by other GIMP or Inkscape users. Blank looks. Lesson ensues.
Relying on a specific software package is fine. *Depending* on it is risky. And *not being able* to design using anything else because of some marketing-infused mental block just means you're spoiled and/or ignorant. Bravo for the true creativity displayed in the article.
But he was *making money*, get it? Coin - money...
Anyway, the interesting thing here is not that he designed something with free software, people do that all the time, but that his design won. Of course I didn't read the article, but A assume his was not the only entry, and that at least some other entries were prepared with proprietary software.
So it wouldn't be "an author wrote a book using OpenOffice" but rather "a book written using OpenOffice won some prize". Of course books created by free software regularly win top places at typography contests, so it would still not be that unusual.
There is, however, certain feeling among both professionals and public that in the area of graphics design, proprietary software rules, and using free software gives you a serious handicap. That is what makes this interesting.
AccountKiller
So, basically, shovels are better than back hoes because with a shovel you can make both small and big holes, but with back-hoes, you can only make big holes. However, what you aren't taking into account is that while backhoes can't make small holes, they are way more efficient at making big ones.
And just for the record, a "small hole" is a low-level project, such as an operating system, and a "big hole" is a higher-level system, like a software program.
I'm not saying that C# is better than C, just that they have different purposes and are therefore better at different things.