From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] move zlib source from ghostscript to ape/lib/z and update to latest zlib
Date: Tue, 3 Mar 2020 20:05:29 +0900 [thread overview]
Message-ID: <33BA722BBB374A6495660029377F354F@hera.eonet.ne.jp> (raw)
In-Reply-To: CAFSF3XNHKSDka2O62VeSN_wrvYEYskNobURBGMYP-aR-nmv+cw@mail.gmail.com
I like the (1) way.
To follow every updated external library is worse.
This kind of topics should be discussed for individual cases, I think.
Kenji
> in general part of the beauty in plan9 is that some geniuses found
> abstractions that are so much better, that reimplementing the
> functionality the plan9 way is simpler than porting a library even
> once, which saves us 1) the work of porting it even once 2)
> maintaining a mirror image of some external bikeshedding process.
>
> it's kind of rare that 2) or 1) alone is less work than reimplementing
> everything on plan9.
>
> doing both 1) and 2) seem completely hopeless for most modern libraries.
next reply other threads:[~2020-03-03 11:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 11:05 kokamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-03 6:36 kokamoto
2020-03-02 23:08 kokamoto
2020-03-03 0:49 ` Steve Simon
2020-03-03 1:01 ` ori
2020-03-03 10:06 ` hiro
2020-03-03 10:08 ` hiro
2020-03-03 10:12 ` hiro
2020-03-03 14:01 ` ori
2020-03-03 13:58 ` ori
2020-03-02 5:15 Lucas Francesco
2020-03-02 8:33 ` [9front] " cinap_lenrek
2020-03-02 14:41 ` ori
2020-03-05 19:17 ` cinap_lenrek
2020-03-08 23:44 ` Lucas Francesco
2020-03-16 3:28 ` ori
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=33BA722BBB374A6495660029377F354F@hera.eonet.ne.jp \
--to=kokamoto@hera.eonet.ne.jp \
--cc=9front@9front.org \
/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).