Quote:
Originally Posted by kushalkoolwal
But at the same time even if we assume that programs based on shell scripts are simple, still there is time cost associated in developing a pretty long and a relatively complex script and that could potentially be a good opportunity to earn some cash, ehh? May be.
|
Note that earning some cash and making your software proprietary and/or
hiding the source do NOT necesarily go hand in hand. In fact hiding the
source can very well hinder sales if you're a small shop because customers
like to know that if you disappear that can find someone else to do
maintainance on the software. For the last ten years my bills and
those of my employees have been paid by a software package we did in Perl.
Redhat Inc. has of course made millions form Anaaconda and other open
source software they've written.
For our main product, the source is available to all users so they can
inspect it, understand the system, and do customization or maintainance
if required. In fact, very few of them do any customization - they come
to us for that because we understand the system best and have done similar
customizations before. They like knowing that tey have FULL use of the
software they bought - not some encrpyted thing that will become useless
if an update is needed to work with one some new system or something.
We haven't had any problem with people copying our software and us losing
business from that. It just hasn't been a problem and probably wouldn't
be for you either.
While our source is available to all customers, our main product is not
actually free software because we don't give redistribution rights.
Customers can modify the software but can't LEGALLY resell it.
(Not that people on the internet pay much attention to copyright law.)
However, customers like the fact that our license says it will
be licensed under the GPL if we ever cease to support it for any reason.
Other software we sell is GPL. People COULD get similar software
elsewhere without paying for it, but they come to us with cash in
hand because they want our help selecting and installing the best
software for the job, they want our modifications, and they want us
to be available for questions after the sale.
If license issues are causing you in trouble and you're writing
Linux, FreeBSD, etc. software you might try selling it under the GPL
and see how that goes. The doesn't mean you can't sell it and make
good money.
Quote:
Originally Posted by kushalkoolwal
But at the same time even if we assume that programs based on shell scripts are simple, still there is time cost associated in developing a pretty long and a relatively complex script
|
My assumption isn't that shell scripts
ARE simple, but that they
SHOULD be.
I'm saying that if what you have in mind right now is "pretty long and
relatively complex", then it's going to be more complex by the time it's
ready for release, even more complex a year later after new additions
and features are added, and so SHOULD be written in a programming
language like Perl, Python, etc. rather than in a user interface
language like bash. C might be appropriate, but if the shell was
your first instinct than Perl is probably an appropriate "one step up".