From: Blake McBride <blake@mcbride.name>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] mk time-check/slice issue
Date: Thu, 19 Dec 2013 12:40:28 -0600 [thread overview]
Message-ID: <CABwHSOs0TRSw6fF8Kd_Ww6Vdb5K=OSgxZ-kszpZ2c639Fw0oyA@mail.gmail.com> (raw)
In-Reply-To: <dc1702425bf92852e33537a89bd0c78d@9srv.net>
[-- Attachment #1: Type: text/plain, Size: 2473 bytes --]
On Thu, Dec 19, 2013 at 11:07 AM, <a@9srv.net> wrote:
> // If you are working on a project, edit some files, and then
> // perform a mk, if files you haven't changed get built, I for
> // one would constantly question myself, about whether or
> // not I changed that file. It would make things confusing.
>
> It's confusing because it doesn't match your expectations,
> but that's just as much because you're misunderstanding
> the intent of the tool. mk is not a tool for checking for
> changes, it is a tool for ensuring things are up to date. It
> just isn't designed to provide what you're looking for. That
> isn't to say that what you're looking for is unreasonable,
> but mk is not the tool to provide it.
>
> As an aside, I'd suggest learning to simply not worry about
> it. Internalize the fact that mk will sometimes rebuild things
> that don't strictly need it, but will ensure that things are up
> to date, and you'll have an easier time of it.
>
> // I for one favor practical usefulness over theoretical
> // correctness.
>
> You have not demonstrated anything that significantly
> impacts mk's practical usefullness. The fact that mk will, in
> some cases, rebuild things which don't need it doesn't
> significantly impact its utility for its intended purpose.
>
> In Plan 9, the heirarchy of values is different from other
> systems. Correctness (theoretical or otherwise) and
> elegance come above utility. That's not to say there are
> no tradeoffs in the system, but if you're going to give up
> even a little bit of correctness or elegance (environment
> variables?!?), you'd best be prepared to demonstrate a
> rather substantial utility gain. Given how much use this
> community has gotten out of mk over the past ~27
> years, I think it's safe to say we're not sold.
>
> Anthony
>
>
>
What I am beginning to understand from comments like this is that there is
a "club Plan-9". Everything ever done by the originators of "club Plan-9"
is correct, period. No mater what exceptions, special cases, or good new
ideas occur, they are wrong and we will find some way of rationalizing
"club Plan-9". Anyone can join "club Plan-9" if you buy into that
assumption. The main purpose of Plan-9 forks (with some exceptions) is to
port to new hardware. Messing with the premise of "club Plan-9" is
significantly frowned upon and attacked.
Just a newbie's (with 35 years experience) perception.
Blake
[-- Attachment #2: Type: text/html, Size: 6204 bytes --]
next prev parent reply other threads:[~2013-12-19 18:40 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 22:01 Blake McBride
2013-12-18 22:08 ` Matthew Veety
2013-12-18 22:42 ` Blake McBride
2013-12-18 22:16 ` erik quanstrom
2013-12-18 22:46 ` Blake McBride
2013-12-19 5:40 ` erik quanstrom
2013-12-19 6:07 ` Bakul Shah
2013-12-19 10:59 ` Charles Forsyth
2013-12-19 14:21 ` Oleksandr Iakovliev
2013-12-19 14:58 ` erik quanstrom
2013-12-19 14:52 ` Blake McBride
2013-12-19 14:55 ` erik quanstrom
2013-12-19 15:58 ` Blake McBride
2013-12-19 16:30 ` Tristan
2013-12-19 16:37 ` Blake McBride
2013-12-19 16:40 ` Jacob Todd
2013-12-19 17:05 ` Blake McBride
2013-12-19 17:24 ` Tristan
2013-12-19 18:30 ` Blake McBride
2013-12-19 17:59 ` Steffen Daode Nurpmeso
2013-12-19 17:07 ` a
2013-12-19 18:40 ` Blake McBride [this message]
2013-12-19 18:58 ` Kurt H Maier
2013-12-19 19:06 ` Matthew Veety
2013-12-19 19:07 ` Kurt H Maier
2013-12-19 19:20 ` Blake McBride
2013-12-19 19:27 ` Kurt H Maier
2013-12-19 19:42 ` Blake McBride
2013-12-19 20:02 ` Kurt H Maier
2013-12-19 20:18 ` erik quanstrom
2013-12-19 20:23 ` Kurt H Maier
2013-12-19 19:35 ` a
2013-12-19 19:09 ` a
2013-12-27 10:16 ` dexen deVries
2013-12-19 19:09 ` erik quanstrom
2013-12-19 19:29 ` Blake McBride
2013-12-19 19:39 ` Gabriel Diaz
2013-12-19 20:15 ` Richard Miller
2013-12-19 20:28 ` Blake McBride
2013-12-19 20:45 ` Richard Miller
2013-12-20 15:23 ` Aram Hăvărneanu
2013-12-19 19:12 ` Skip Tavakkolian
2013-12-19 19:22 ` Blake McBride
2013-12-19 19:43 ` Rudolf Sykora
2013-12-19 19:58 ` Blake McBride
2013-12-19 19:26 ` sl
2013-12-19 10:01 ` Richard Miller
2013-12-19 15:01 ` erik quanstrom
[not found] <CAC0DbM5safEHO_MFpBazvvH6CcGQXGTow-Fe7fkqkP6GrU1Xzw@mail.gmail.com>
[not found] ` <CAC0DbM7S-xZvOSDwB6KoWH2X8ny_57F9mBE7gaB_BuWR5RSJiw@mail.gmail.com>
2013-12-18 23:09 ` Jason Catena
2013-12-19 5:47 ` erik quanstrom
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='CABwHSOs0TRSw6fF8Kd_Ww6Vdb5K=OSgxZ-kszpZ2c639Fw0oyA@mail.gmail.com' \
--to=blake@mcbride.name \
--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).