From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 17 Jun 2013 20:20:56 +0200 From: tlaronde@polynum.com To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20130617182056.GA1261@polynum.com> References: <4C33D9D9-6A99-43E0-A621-0D137564F441@lsub.org> <10DB3CE7-1903-4D06-8784-1416398302CE@lsub.org> <47813B77-1111-4199-8C51-726B55B39BB0@gmail.com> <108c856b42a813c1a5425ed4a4978387@ladd.quanstro.net> Mime-Version: 1.0 In-Reply-To: <108c856b42a813c1a5425ed4a4978387@ladd.quanstro.net> User-Agent: Mutt/1.4.2.3i Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: Re: [9fans] 9n Topicbox-Message-UUID: 66571a2e-ead8-11e9-9d60-3106f5b1d025 On Mon, Jun 17, 2013 at 02:01:08PM -0400, erik quanstrom wrote: > On Mon Jun 17 12:55:25 EDT 2013, aram.h@mgk.ro wrote: > > > a lot of effort has gone into making code public. > > > > But it would be zero effort if code wouldn't be secret in the first place. There is code that is neither secret nor published. Code that does "the" or "some" job for the writer but that the writer does not want to maintain (for a public audience). I have the example for kerTeX: I use RISK, my own framework, that is not a precious proprietary code with lots of cutting edge and research features, but simply something that does the job for me and that I didn't want to support for others. It went publkic by side effect (and the support will be limited to kerTeX use). -- Thierry Laronde http://www.kergis.com/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C