But is it? There seems plenty of reason to doubt whether the approach is either new or open source. My original concept when proposing CRE Loaded commercialization was to charge a standard fee per copy distributed with a 30 to 90 day support window, following which support could be obtained on a contract basis. Revenues would be further augmented by internally developed documentation and education offerings made available both directly to the public on Chain Reaction’s own site, and via a distribution network of existing community vendors. The value of the software would be increased by ongoing addition of new features designed and built in house, and refactoring of the core code to bring it into alignment with the current PHP and MySQL feature sets and changes in the security environment.
What has emerged appears to be little more than SaaS without the second S. Here is why.
The “manual” posted on the latest incarnation of their website is a thinly disguised knock off of Kerry Watson’s 6.2 Users Manual. They may argue that there are few other ways to state the programs use, and that just may be. But why can’t the ‘designers’ of the software do any better? They should for example, have access to and include information on input formats and boundaries, and systemic capabilities and limitations which are not readily available to the non-programmer. Such information is not, as of the date of this writing, available in their “users guide”. Their “educational program” consists of a page buried 3-5 levels deep in their site which asks the users to inform Chain Reaction of their educational needs so that content can be developed. So much for educational and documentation support.
Their new releases are “subscription” based. But there is some room for question as to just what users would be subscribing. What does Chain Reaction deliver in return for its charges?
Read More
2 Comments