The catch in situations like this is that it may have never been written in the first place if Laurent wasn't able to take the time and dedicate the energy full time to build it. Personally, I'd rather fund continued development of it with a license than never to have had it in the first place.
--Jeremy On Thu, May 3, 2012 at 3:04 PM, Perry E. Metzger <pe...@piermont.com> wrote: > On Thu, 03 May 2012 13:15:52 -0500 Ian Ragsdale > <macr...@ianragsdale.com> wrote: > > That said, I'm wondering if/when any of this will become open > > source? It's been a long time since I trusted proprietary code > > more than open source stuff. Open source projects can aways be > > forked or maintained by someone else, but if a proprietary company > > drops support for whatever reason, your codebase depending on them > > is in trouble. > > > > I'm not trying to suggest in any way that you guys would do that, > > but it does make me a little nervous suggesting using this to any > > of my clients. > > I have to agree. I have no fundamental problem with paying for stuff, > but I do have trouble with a code base that can't later be picked up > and actively developed by someone else if the initial developers > vanish. Apologies for injecting any negativity here. > > Perry > -- > Perry E. Metzger pe...@piermont.com > _______________________________________________ > MacRuby-devel mailing list > MacRuby-devel@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > -- http://jeremymcanally.com/ Positivity every morning: http://goodmorninginterwebs.com Bowties, ties, and more: http://wickhamhousebrand.com
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
