I'll have to look into that if I find it fits my needs, though I think that the Jenks Project needs to be open source if my plans for it are going to work out the way I'd like.
-----Original Message----- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Mark Hurd Sent: Tuesday, July 9, 2013 10:22 PM To: ozDotNet Subject: Re: the Open Source community for .NET developers: the value of joining and developing OS VS. for-proffit development "It's not truly hidden unless you go to great lengths to obfuscate it." That's true except when you don't actually provide the software to the consumer. Software as a service makes it quite feasible to provide great technology without giving out the source or binary code. -- Regards, Mark Hurd, B.Sc.(Ma.)(Hons.) On 9 July 2013 12:03, Stephen Price <step...@perthprojects.com> wrote: > ah ok. Only reason you would hide your code is if it is a secret, as > in part of your business intellectual property. An algorithm, or > whatever that no one else has, and that sets you apart from your > competition. It is important from a business perspective to keep > what's yours as yours. Arguably, I guess. That would be situations > where your income comes from your product and that people are prepared > to pay for it because no one else can do what your product does. > You can make money from selling your time, or a product, or for > providing a service. When you say hiding your code I assume you mean > closed source versus open source. It's not truly hidden unless you go > to great lengths to obfuscate it. It's not a bad thing to want to > protect your IP. Same as its not a bad thing to want to have open > source code. Really depends what you are trying to do. As for making > money from coding, yeah there are numerous ways. There's apps in > market place, Ads, freeware, Shareware. In app purchases, and donations. > Contracting and Permanent jobs for someone else. > Write a product or service and charge people to use it. All part of > the excitement and challenge of working as a developer. :) So yes I > agree there's more than hiding your code and charging for your stuff. > I do detect a hint of judgement or invalidation against hiding your > code and charging for it. It's not right or wrong, but thinking makes it so. > >
