9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Richard Elberger" <richelbe@richelberger.com>
To: <9fans@cse.psu.edu>
Subject: RE: [9fans] source code as data not text
Date: Tue, 19 Jun 2001 15:52:41 +1200	[thread overview]
Message-ID: <JNENKONOPMBLIHLMIJEDGEKGCBAA.richelbe@richelberger.com> (raw)
In-Reply-To: <20010618152511.B7DBA19A08@mail.cse.psu.edu>


>and while i'm not entirely clear on what exactly lac was refering 
>to, can you
>deny the usefulness of being able to "grep ^foo(" in code, or 
>suggest that a
>databasse system would make that easier somehow? again, as noted earlier,
>db-based source code systems are another failure to use the little-tools
>model appropriatly.

select .. from .. where ..

What's the difference?  The only difference I see is every time you grep you do an fopen/fclose.  With databases, information can even be cached, and can perhaps be "smarter" through cross-referencing.  While this is a generalization on a massive scale, I think it is comparable.

>
>and as dan points out, SCCS/CVS style stuff is not what's at issue here.
>

But it is -- editing, checking in/out, collaborating, etc.  To just have another editor is short-sighted.  Imo, Rational Software almost has it 100% right -- they have process, tools, and repositories integrated with 3rd party products.  They just don't have the full-blown integration/collaboration that's needed.  

>//In fact, you'd be surprised how many big software companies are already
>//moving that way...
>
>much to my dismay, i believe you. but then, i'm often suprised how many big
>companies are doing _lots_ of things i consider stupid. PeopleSoft, anyone?

But people still buy their software ... why?  Perhaps to the customers it adds value.  In any case, internal process is different than how products realize the customer's need.  Maybe your comment is about internal-Peoplesoft, which I know nothing about...

>
>the most involved syntax highlighting i find useful is 
>paren/bracket/quote/&c
>matching. i could imagine an editor that did that well (acounting for the
>language-specific escapes and such) being quite nice. more than 
>that i've not
>found useful, and it's distracting and damaging to people who're learning.
>and what acme's got now is good 95 times out of 100.
>-α.
>
>

In your particular case... acme still tires me out. When using Inferno, I use that plain-text editor instead of acme -- with the syntax highlighting for limbo.  I think it's nice to have the option.  I just wish there was a nicely integrated source management system so I wouldn't have to worry.

-- rich






  reply	other threads:[~2001-06-19  3:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-18 15:24 anothy
2001-06-19  3:52 ` Richard Elberger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-28 21:17 Boyd Roberts
     [not found] <dhog@plan9.bell-labs.com>
2001-06-18 18:48 ` David Gordon Hogan
2001-06-18 21:31   ` Steve Kilbane
2001-06-19 21:03     ` Richard Elberger
2001-06-19 21:31       ` Steve Kilbane
2001-06-19  7:36   ` Richard Elberger
2001-06-28 22:17   ` Boyd Roberts
2001-06-18 14:45 anothy
2001-06-19 16:51 ` Barry
2001-06-18  7:45 nigel
2001-06-18  7:43 nigel
2001-06-18  9:07 ` Laura Creighton
2001-06-28 21:00   ` Boyd Roberts
2001-06-28 22:02   ` Boyd Roberts
2001-06-18  0:31 Matt
2001-06-18  8:52 ` Laura Creighton
2001-06-18  9:13   ` Matt
2001-06-18 10:02     ` Richard Elberger
2001-06-18 14:56   ` Dan Cross
2001-06-28 21:56 ` Boyd Roberts

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=JNENKONOPMBLIHLMIJEDGEKGCBAA.richelbe@richelberger.com \
    --to=richelbe@richelberger.com \
    --cc=9fans@cse.psu.edu \
    /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).