The risks of open source solutions
It is quite a fundamental problem. On the project often operates a number of enthusiasts with a different experience and a different approach. There is a programmed object, procedurally, there is an attempt to some MVC templating system or architecture, but ultimately fails to push through, so the code will remain fragments of something that actually has nothing to do there. One developer works better with this, the second, rather with something else ... and the result? An odd, inconsistent conglomerate.
Elementary errors and deficiencies
Not quite so rare that one meets with the opensource project or one of its component, where they do not treat the inputs from the user (which is absolutely crucial security risk), which does not address any local specifics (just all have Web sites in English, so you'll have it in English, what you want accented or invoice in Prestashopu human data format). Who ever put it should be Yet, confirmed to me that the correction of various errors or imperfections, so that this kind of dignified work, it takes a week to 14 days. If you want to have a project that is based on the fact that absolutely have no idea what where who wrote is opensource ideal solutions.
Of course, a must for Wordpress or Joomlu there are tons. plugins, but as well – there is nothing so desperately setting an inflexible as opensource. The problem lies in the fact that years of development have made the most monstrous and complex enough opensource molochy. Modification of any of the prkotiny often involves modification of the dozens of things that depend on it, and sometimes even not possible it all traced and treated. This man gets into a situation he believes in functionality, but I don't know how it is possible that it works. And it is pretty bad--no plugin does. And study the Moon, who thought, during which time you can do a decent shop on your own.
It is a matter of partly based on the point above. All opensource systems (e-shops, even those so-called publication) are based on the assumption that it is necessary to prepare most of the functions that it was what the most versatile. The apparent advantage has two consequences: on the one hand you have in 80% of the features that you do not use, so just get in the way, it creates a sophomore moloch, which is AMD's so desperate that it is evident to the naked eye and are not on it (try to be such a Joomlu and its speed of loading each page; see for yourself). This is invaluable when the client prepares the tailor-made applications and only with those features it needs.
Major security risks
Must say that the situation is a little better, but still it is not opensource product for each granted that treats all inputs from the user, that is immune to SQL injection or various theft of sessions. If someone hackne private blog, nothing happens. If someone hackne commercial web with some private data (names, passwords, card numbers, etc.), it is for the operator of a huge bummer. Not to mention about the installation of various "plugins" from a variety of šikulů, where a person with absolutely no idea what it is and what it installs (and sometimes still has good feeling, that application's enriched).
Zero responsibility to the creators of the system
Which there is no pablum. Most opensource is used under a license from the public UNDER the GPL, is that you, as the product is, therefore, no bullshit, and any options to recover damages which product someone causes (e.g., theft of credit card numbers because of the ease of hacking the system, kleknutí the server because of poor performance, etc.).
Poor and invalid HTML code
This is all ill the opensource systems, dare I say, without exception. The Layout of the pages, and in 2011 it generates into tables, ideally five nested (yuck!), the code is pasted together, as to whom came under the arm (a piece of HTML, XHTML and even with errors, a bit vysmrklý for some wordovského editor style directly in the code – twice! ugh!), the result of absolutely desperate. And the only thing you can do is to sit down over it and after a week it unite and for someone to fix it. It really pays off.
Licensing and legal issues
If you have programmed an application, it is clear that you are not obliged to give to the next free distribution. For this obligation to be opensource can-in the text of the license can be a condition that, if you use as part of another work of art, the new work automatically becomes opensource. Depends on the specific text in a specific license – but nobody reads it anyway, right? In addition, the legal complexity of what is or is not for free, with all the consequences vary from State to State, he knows about the devil and rely not on anything today. Then you weren't a surprise, something that you own, but actually, it's you.
Harder to remove critical errors
This is also expressed by the smallness of the. If you are not the person directly involved in the development of opensource product will be pretty problematic in the case of some critical mistakes her trace – you must first become familiar with the application, find the section of code that provide the functionality (and probably will be fragmented after ten on dependent methods,