9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Aram Hăvărneanu" <aram.h@mgk.ro>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] mk time-check/slice issue
Date: Fri, 20 Dec 2013 17:23:11 +0200	[thread overview]
Message-ID: <CAEAzY39uup13ve4ah5f+HRuMsy_RwPQ0CjsiSNPX-G1Ste=DYA@mail.gmail.com> (raw)
In-Reply-To: <361faa09f7cfac71931b78a5edcc2b43@hamnavoe.com>

The "problem" discussed here is caused by low-resolution timestamps. The
solution is to to increase the resolution of the timestamps, not to add
hacks to the mk tool. Adding hacks and special casings inside tools is
one of the main reasons why Unix is so clumsy and hard to use. Look at how
networking was added to BSD. A quick hack to the kernel that expanded the
API surface and required writing new programs. On Plan 9 we know better.

Increasing timestamp resolution comes at a cost. It is a problem too
minor to be addressed on its own. If there's ever a revamp of the
protocols for some other, more fundamental reason, perhaps it is worth
addressing. Perhaps not. See IX. Making lasting changes too early is
also a mistake Unix made.

I'd also like to note that if low-resolution timestamps became observable
in mk, the thing you are building compiles so quickly that it's unlikey
to cause any wasted human time. Avoiding solving problems that exist only
as academic exercises to keep complexity down is also one good trait of
Plan 9.

-- 
Aram Hăvărneanu



  reply	other threads:[~2013-12-20 15:23 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
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 [this message]
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='CAEAzY39uup13ve4ah5f+HRuMsy_RwPQ0CjsiSNPX-G1Ste=DYA@mail.gmail.com' \
    --to=aram.h@mgk.ro \
    --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).