in reply to On open sourcing your applications
in thread Restricting access to cgi source

I was thinking after my previous post, that irregardless of whether the source is open or closed, if the end product is good, or fills a niche, someone is either A) going to extend/refine it, or B) recreate it in some shape or fashion

So given your feelings, how would you suggest they go about making money off their creation, without losing their edge over the competition. I personally am adamantly for open source, but alot of people out there aren't.

You have been in this field a long time and more than likely have garnished a bit of wisdom over that time. Can you provide suggestions in regards to a (better|different) way to handle this given scenario?



/* And the Creator, against his better judgement, wrote man.c */

Replies are listed 'Best First'.
•Re: Re: On open sourcing your applications
by merlyn (Sage) on Jan 27, 2003 at 16:34 UTC
    Yes. In very simple terms, be good to your customer, and they will pick you for the followup work.

    If you treat your customers like children, by locking up source, and nickeling them to death, they will rebel like children.

    -- Randal L. Schwartz, Perl hacker
    Be sure to read my standard disclaimer if this is a reply.

    A reply falls below the community's threshold of quality. You may see it by logging in.