Re: [9fans] unknown error message

["Mathieu Lonjaret" <mathieu.lonjaret@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 557 bytes --]

Yes, it can be easier in a sense that you sometimes get the explanation
that you would not have gotten in a obvious manner by reading the code.

If I don't need the answer to the issue right away, and if I want to work
on something else in the meanwhile, it can be better to wait and see what
you wise guys come up with, rather that going head first and grok the
whole context where the piece of code is. Especially if I'm unfamiliar
with that part of the code.

Yes, it's a form of lazyness, but not just for the sake of being lazy ;)

Mathieu

[-- Attachment #2: Type: message/rfc822, Size: 4113 bytes --]

From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans]  unknown error message
Date: Sun, 13 Jun 2010 22:46:27 -0400
Message-ID: <20d109f0282a31f9707bb70db11c0864@kw.quanstro.net>

> Thanks, that's what I was curious about. shoulda grepped but figured
> one of you would know off the top of your head. :)

is posting to 9fans now easier than grep?

probablly not.  recently i've been working with a
few non-plan 9 guys, and the ones that take the
time to look at the system are at first appalled
by the simplicity.  that's it?  really, that's it.  i've
learned to ignore that.  inevitably, a question
similar to this thread comes up.  how to i find xyz.
i get xyz error message.  well, g xyz /sys/src.
that's it?  really, that's it.

i think the complexity of most systems can knock
one of one's rhythm and forget that it can be
as appalingly simple as grep.

plan 9 is fairly unique in that it's a system one can
reasonablly hope to understand by reading the source.
that's it?  really, that's it.

- erik