On Sunday 22 February 2004 23:01, Gil Freund wrote:It's not always a solution. Even if they do give the source to a third party to cover
Actually, this is not a good example. Magic was delivered in two flavors - developer and run time. In order to modify the code of the application you needed the developer version, as well the developer.
I have used Magic for many tasks back in the late 80's - early 90's. What I tried to point is that using proprietary tools (Magic is just an example they used) binds your project strongly to the upgrade cycle of the tool.
While this affects OSS tools as well. It is less problematic: - There are no direct costs to upgrade. - As long as there are users, you are not *pushed* to upgrade by marketoids.
Such as:
http://www.bigwig.net/ampic/soar/
Ok. You got a point. Community driven apps may be built with proprietary tools and be maintained...(still I wonder about the costs in this case).
for their being closed down, it might require a non-existing environment.
In our case, I happened to work with veterans of Magic, and even they couldn't
get me the right developer version for Magic in order to update the software.
Many times the software also requires old environments like DOS or such.
The club was stuck with this software for over a decade because of this, if
they used open-source even of that other time (e.g. probably C or C++ or
Pascal?) then we would have had a better chance at upgrading the existing
software.
I still hope to play on this one.
Thanks.
================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
