Recently the owners of a popular web site have had their site shut down for using an open source (commonly known as open source) application. The move was prompted by the administrators because their business model failed to work without the application. In their eyes, this proves that open source is not a successful methodology for software development. However, I disagree that the trend of open source is not a bubble. I believe that the inherent qualities of the programmers who refuse to get into the habit of proprietary application development spoiled the initiative. Furthermore, I think the quality and tradition of programming languages themselves expose the developers to risk in the open source application development. I am definitely not against open source but I believe open source poses more risks than it solves. The open source application development can be divided into three parts: the application developer’s part is the maintenance and support of the application. The business part is the development of the open source as a service platform. The third part is the customer’s part, which includes the consumer base of the application. The first part of the initiative is really the maintenance phase. Vendor service packs and upgrades are a regular event for this part of the process. The software application owners should invest in preventive maintenance because preventive servicing can save the life of their application. The maintenance costs can be cheaper for the open source vendor of the software. Since the software applications run on common hardware tools, the ability to do routine, manual maintenance is normal and reliable. For the open source application development vendor, the maintenance costs are usually higher than the development costs. Naturally, the higher maintenance costs in the long run will affect the cost of the software implementation. Next comes the part where the application is going to be distributed to the users. This is where the customer service is going to be provided. Installation is going to be sequence of processes. When the application is installed at the customer’s location, the customer defines the access rights of the different users. The vendors provide the access codes which are authenticated through X.25 bits Using the Universal Description and Identification Systemhttp://UDIS.Usenet.edu/, vendors can establish the user’s account. The accounts can be a holds tab or a checkbox. Also, the customers can be allowed to download software updates that are relevant for their login. These updates are sent by UDT code. Any user can access the software without a password. This enables the vendors to monitor the user’s logins. Once the software is installedhttp://www.microsoft.com/downloads, the customer can logon to the forum. The logon details are handled by the forum software vendors who handle the encrypted forum password. These vendors can easily store the forum name, user’s logon details and the new authentication Identity for the user. The encrypted forum password is used to encrypt the logon details. It is the vendors duty to set the forum permissions for the users. Once the software is installedhttp://www.microsoft.com/downloads, forum software, the customer can create an account by answering the related questions in the registration form located in the support center documentation.