9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Robert Raschke" <rtrlists@googlemail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Acme without Flamage
Date: Wed, 20 Aug 2008 16:47:25 +0100	[thread overview]
Message-ID: <6a3ae47e0808200847i49d15364q55f2adddacedac32@mail.gmail.com> (raw)
In-Reply-To: <384332.12907.qm@web57601.mail.re1.yahoo.com>

One of the central tenets of Plan 9 is that everything is a file. So
all file based activities are really, really easy.

Most OO programming appears to follow a more DB oriented style (at
least those with horrendous packaging/module mechanisms). That files
are used to store your programs appears to be incidental. Therefore
using a file oriented system when programming something like Java is
painful, to say the least.

Thus, acme is very probably not the right editor, unless you are in
complete control of the code. But I would say the same holds for vi or
emacs. Its just that those two have had a lot of additions poured into
them that were inspired by the IDE world.

Acme is supremely fabulous when you are in complete control or if
you're programming using a language/environment where there are no
strange rules on where your files have to go (the underlying OO DB,
essentially).

Initially, all that replacing vi/emacs with acme does is change your
habits from keyboarding to mousing. All the pain you get from the
"bad" code remains the same. Some of the IDE inspired features in
vi/emacs may help lessen that pain slightly. But to get a more radical
change, I'm afraid using a proper IDE is where it happens. Welcome to
objects, good-bye files.

Robby



  parent reply	other threads:[~2008-08-20 15:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 15:12 Wendell xe
2008-08-20 15:38 ` Tom Lieber
2008-08-20 15:47 ` Robert Raschke [this message]
2008-08-20 17:14 ` sqweek
2008-08-20 17:42   ` David Leimbach
2008-08-20 19:23     ` Gorka Guardiola
2008-08-21  9:06       ` Paul Donnelly
2008-08-21 13:35         ` David Leimbach
2008-08-22  4:57         ` sqweek
2008-08-22  8:38           ` Paul Donnelly

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=6a3ae47e0808200847i49d15364q55f2adddacedac32@mail.gmail.com \
    --to=rtrlists@googlemail.com \
    --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).