A software development company since 1986
Anti Open Source
I am against open source software. The whole concept is not productive. It could be, but unfortunately the premises of shared logic is wrong, or rather the implementation is wrong. Free applications is great. Sure anyone can give me an application for free, it will work or it won't. This generally takes a few minutes to determine, I can keep it or I will immediately delete it. Of course you must weave through the licensing maze, you may not own your own work. The security issues will have devastating effects on any commercial product, or any commercial use of a product developed with open source code.
What I am against is wasting time on free libraries or free source code to an application. The general purpose of the free libraries is to handle logic that is missing from our software development environment. Each system is a closed environment with its own set of solutions, however the problems are common; Characters, Strings, Numbers, Dates, Image, Video, Audio, Parsing, Search and Replace, Storage, Transport, Graphics, Math,... a list of maybe just a few hundred topics that should be globally solved for every application.
One of the problems of open source is that it is free, you get what you pay for. Even worse is a false sense of productivity, failure to address the compete problem, and the layering the logic of unknowns. It is the layered logic of unknowns that is not being addressed. The watered down solutions based on other watered down solutions to the point of ultimate stagnation of technology, if we have not already reached this point in our development.The real solution of openness is to create a system that permits software developers the freedom to develop software. The issue is the 20 lines of code, not millions, that restricts access to logic that blocks everyone from performing their jobs. If a battery the size of a quarter, could be made to run a Mack truck for a year, would it be allowed to be made? It is just about that extreme for the current state of software development.
I am all for people working together, however you must first understand what that means. With over forty years in software development I have yet to find one example of shared knowledge. It is not the intentions that fails but rather the reality of sharing. Any overhead attached to an effort that does not benefit both parties equally will fail.
It could work great with a slight alteration to concept. Almost no work is involved, take what we have an alter the intention of the product.