Jump to content

Por que Software Libre

From ourproject.org wiki

Why Free Software

Copyright © 2003 Rexursive. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the licence is here.

It's Historical... After I moved to Australia in 1996, a whole new world of computing opened op to me. The projects were bigger, the stakes higher and there was more money involved that I have ever seen. I was green, so I spent two and a half months looking for a job and in the process got to attend a group selection process at one of the Sydney's computer course companies, mostly servicing the needs of local corporations. And I'll never forget what we were told that day by the owner of the company: "There are three words you have to remember: Microsoft, Microsoft and Microsoft." It was pretty obvious who was controlling the market, even then.

Well, finally landed a job of R&D engineer for a local computer manufacturer. Not exactly my cup of tea, but it turned out to be quite educational. With one of the engineers gone, the company was left with nobody that knew anything about Windows NT. Not that we sold that many, but somebody had to know how to at least install the damn thing. So, I took NT 3.51 CD's and installed it on my workstation. A bit later on, NT 4 Beta was out, so I tried that too. Anyhow, in about a year's time, I was pre-installing all Windows NT 4 shipments and ended up giving an NT course to the rest of the technical staff in the company. My favourite line was: "To understand NT, you have to love it." That's how naive I was at the time. NT was the star on the rise, displacing Netware left, right and centre. Microsoft was pronouncing Unix dead. So, I sheepishly followed, without proper understanding as to what implications my decision had on my technical skill set.

Sometimes bad things happen that turn everything upside-down and end up changing one's life for the better. Well, the company's premises burned to the ground and we were forced to set up a temporary office nearby. Unfortunately, no unit was big enough for the whole company, so two were rented out, some 300 metres apart (by air). The first thing for all the technical staff to do was to build and set up all the servers. Since we wanted to migrate to NT 4 anyway, the old Netware 3.11 box was never rebuilt and was replaced with NT, with all the backups restored to it. When things settled a little bit, I wanted to connect the two offices, with only two analogue phone lines that were available. And I took a stab at setting up the multilink PPP connection between two NT servers. Initially done through RAS and some registry hacking, later on replaced by (according to Microsoft) more capable RRAS, the routing actually worked. Well, some of the time it did. RRAS turned out to be so unreliable that I ended up walking between offices to fix things, many times during the day. I wasn't really happy about that. Not to mention that most changes I had to make to the configuration needed a reboot - quite annoying for both myself and the users. Other nasty bits of NT 4 also surfaced and it turned out that every little change required a reboot, including changing options of the print server. Strangely enough, browser installation was required in order to install the web server - something I still fail to understand to this day, followed by a system reboot. It was just silly. There had to be a better way...

Coming from a software development background and with Internet taking off, I was thinking more and more about setting up my own business, something to do with web sites and web applications (although I don't think anyone called them that in those days). So, I started looking into gathering the necessary bits to make it all happen. A couple of PC's networked together would do the trick at first. But I had bigger problems to solve - what about software? Getting my hands on Windows NT 4 Server was easy enough, there were plenty of copies lying around in the company. Burning a copy was also easy, but doing it for real required paying the licence fees. A few grand would be gone straight away, the funds that I could use to buy better or more hardware instead. And that was just the operating system, I didn't even start looking into development tools and all other software I'd need. Things were going from bad to worse. I didn't like my choices. There had to be another way...

I was just plain frustrated, both at work and in my own (still imaginary) venture. Well, the fire that hit the company created another interesting side effect - the most important machine in the whole company, a SCO OpenServer system, also died. Having some Unix experience from my University days, I looked over the shoulders of people that set the new box up. Good memories of hacking in C on old Sun systems (based on 16 MHz Motorola 68020 chips) came back. So, I started looking on the Internet for Unix that I could use instead of NT. That's how I found Kirch's article Unix vs. NT. And that's how bumped into Open Source Organisation. A bit later on, I ordered my copy of RedHat Linux 5.0, straight from the good old U.S.A. It was too good to be true - the CD's contained everything I needed to kick things off. And the best part was the fact that I could copy and install it as many times as I liked without breaking the copyright laws. Development tools supplied with it were the icing on the cake.

At the time, I couldn't fully grasp the importance of my decision. I thought I did a good thing. Today, I know I did a brilliant thing! Just like it promised, free software delivered freedom to use, distribute, copy and modify the software, but more importantly to learn about all aspects of it. The whole switch didn't, of course, happen overnight. Many hours, days, months and years of reading the manuals, following HOWTO's and 'doing it' were needed to acquire the knowledge about the system. I've made many errors in the process (and probably will make for a long time to come), even tried to fix things by rebooting (don't waste your time - it doesn't work :-) But one thing remained steady - I was never afraid that my knowledge will be wiped out by the next wave of proprietary technology. Or that I'll have to spend another pile of money to 'educate' myself again about something I already know (read: gain certificates to prove my level of education to someone else), because it now comes in a slightly different package and there is a new buzz word that describes it.

So, without further ado, here is my list of important facts about free software, based on my everyday experience with it:

1. No Software Tax The immediate benefit from running a free operating system and other free software is licence cost. It just doesn't exist. The more systems you build, the more money you save. Even if you're just a small business, like myself, this one is pretty obvious. I once did a little calculation of the cost of licences, if I were to run proprietary software and wanted to keep it up to date. It turned out that I'd have to fork out thousands of dollars every year. For that money, I could buy myself a brand new box every year!

2. No Vicious Cycle I'm not a big conspiracy theory fan, but this one comes really close. Proprietary software, especially Microsoft Windows and its accompanying software, pushes the hardware limits hard. It is almost a guarantee that the next version won't run in a satisfactory manner on older hardware. Which then causes yet another hardware upgrade cycle, and so on and so forth. It seems as if the two from the Wintel camp have a silent agreement to push more of their products. Free software is not, of course, completely immune from demanding better hardware, but it is far more moderate in those demands. And the fact that it is designed with good old Unix design principle, where every component does its job and does it well, enables it to be customised to suit the hardware budget. You won't find many useful 486 and P5 systems running Windows NT/2K, but you'll find plenty of Linux routers, firewalls, mail relays, DNS servers and what not in those configurations. The vicious cycle of software/hardware upgrades is greatly slowed down in the world of free software, and many times the life of hardware itself forces the upgrade, not the new software. Another, rather interesting phenomenon that is a direct result of the above, is the fact that older hardware can be easily demoted to do less intense tasks while running the latest free software. In such scenarios, the new hardware goes in to improve performance of more intense tasks. The end result is more useful hardware and less potential points of failure per system.

3. No Licence/Media Hassle Every proprietary software product is different when it comes to installation of licences. Some require punching in codes, some only run on a specific IP address or machine. Some need new activation codes supplied by the manufacturer every time they are installed. They are not very often completely trouble free during installation, as far as licences are concerned. You have to make sure your licence certificates are kept safe and accessible when you need them. This then presents itself as a real hassle if you want to set up a test system or demonstrate something on your client's machine. Free software comes completely trouble free here. The best part is that you never have to have any licence accounting in place - you just keep on installing.

I've seen the following so very often in various companies I worked for - the media gets misplaced or lost. For proprietary software, this usually means contacting the vendor to organise a replacement (at a charge) or making a copy of someone else's media. With free software, you can always grab it off the Internet if you misplaced your media. So much easier.

4. No Marketing Lies True free software has no strings attached. There are no lite versions that have the only purpose of luring you into buying the full blown thing. There are no gimmicks. There is just software that can do things. You either like it for what it can do or you don't use it. It is also relatively easy to determine if a free software project is a serious one. The amount and quality of documentation, the number and caliber of developers and their organisation, are, among other things, very good signs. One just has to subscribe to the development mailing list to find out.

5. Reality Based Documentation I found this to be one of the crucial benefits. Most proprietary software documentation is focused on how to solve the problem using the vendor's tools. Most free software documentation is focused on how to solve the problem. The consequence of this is the fact that free software documentation is more honest, contains more information about computing fundamentals (e.g. data structures, protocols, standards etc.) and is generally more fun to read. Coming from proprietary software background, I found out about a number of things in free software documentation that were never mentioned in proprietary manuals. It is also extremely rare for free software to have undocumented features.

6. Blurred Roles It is amazing how Microsoft convinced many that system administrators don't need to understand programming. How does one manage a computer that executes billions of instructions every second without understanding how it all happens? And how does one automate tasks if programming logic is something he/she is unfamiliar with? Free software encourages administrators to be programmers, and it encourages all IT people to be aware of security, networking, protocols, data formats and other computing fundamentals. The borders between roles are blurred out, giving all involved more knowledge and therefore more power.

7. No Buzz Words In order to create pleasing marketing effects, usually by fueling people's desire to be among the best, 'on the cutting edge', proprietary software vendors engage in creation of buzz words to attract new buyers. There is always talk of 'new technology', exclusive to the vendor promoting it. Free software operates on a totally different set of ground rules, usually based around scientific facts, standard protocols and data formats. While proprietary software has buzz words with no real meaning, free software is concentrated on bits, bytes, instructions, hash tables, b-trees, threads, directories, file systems and other verifiable terms, supported by computing theory and practice, reference implementations and source code. This then enables competent IT personnel to make decisions based upon facts, not glossy brochures.

8. Religious Implementation of Standards One of the best features of free software. You can almost bet that free software developers aren't going to wonder off into the wilderness of non-standards. Most implementations are either reference implementations or religiously follow some standard or specification. It all comes from the very nature of free software development - collaboration. It would be impossible to develop free software without having the underlying set of agreed-upon data formats, protocols and specs. Direct benefit is that behavior of free software is very predictable and one's knowledge about it accumulates, rather then being thrown away with each new proprietary technology that comes and goes.

9. Open Source This one is a true classic. It is the ultimate reference and source of documentation. It is also the ultimate power to fix things, understand and improve. It is a guarantee that programmers cannot get away with shoddy code - not in the long run anyway. It also gives free software long term viability and it makes it practically impossible for it to become extinct due to market forces. The usual complaint from NT administrators is that source code is of no benefit to them since most of them cannot understand it anyway. Damn straight! It just shows how much more power an administrator of free software system has.

10. Personal Satisfaction When you spend 8 - 12 hours working on the computer every day, like me, you don't want it to be just about getting the cheque at the end of the month. With free software everyone has a chance to make a difference. The respect and recognition of peers is something that translates into great personal and professional success. And knowing that your contribution made a difference to someone else, feels great.

Final Words This article is by no means finished. As I recognise more facts from my own experiences with free software, I will publish them here. In the meantime, happy hacking!