From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9n
Date: Mon, 17 Jun 2013 20:20:56 +0200 [thread overview]
Message-ID: <20130617182056.GA1261@polynum.com> (raw)
In-Reply-To: <108c856b42a813c1a5425ed4a4978387@ladd.quanstro.net>
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 <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
next prev parent reply other threads:[~2013-06-17 18:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 17:40 Francisco J Ballesteros
2013-06-06 17:49 ` Francisco J Ballesteros
2013-06-17 16:29 ` Jiten Pathy
2013-06-17 16:37 ` Nemo
2013-06-17 16:41 ` erik quanstrom
2013-06-17 16:47 ` Nemo
2013-06-17 16:53 ` Kurt H Maier
2013-06-17 16:54 ` Aram Hăvărneanu
2013-06-17 18:01 ` erik quanstrom
2013-06-17 18:08 ` balaji
2013-06-17 19:48 ` erik quanstrom
2013-06-17 18:20 ` tlaronde [this message]
2013-06-17 18:40 ` Kurt H Maier
2013-06-17 19:06 ` Nemo
2018-05-02 17:14 ` Giacomo Tesio
2018-05-02 17:24 ` Fran. J Ballesteros
2018-05-02 21:25 ` Giacomo Tesio
2013-06-17 19:15 ` Skip Tavakkolian
2013-06-17 19:33 ` sl
2013-06-17 19:47 ` Kurt H Maier
2013-06-17 18:23 ` Jiten Pathy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130617182056.GA1261@polynum.com \
--to=tlaronde@polynum.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).