From: Wendell xe <wendellxe@yahoo.com>
To: 9fans@9fans.net
Subject: [9fans] Acme without Flamage
Date: Wed, 20 Aug 2008 08:12:32 -0700 [thread overview]
Message-ID: <384332.12907.qm@web57601.mail.re1.yahoo.com> (raw)
When I saw the length of the Acme thread, I thought "Wow, so much information!" But it turned out to be mostly flamage. Can't we all just get along?{C}
I don't believe in a single best IDE any more than a single best language. What is best depends on both the particular work and the coder's personal tastes. And, as with programming languages, I think it's good to familiarize yourself with different paradigms.
My nutshell evaluation of Acme is that it is for systems-level coding in C on modest-sized projects. It seems very well designed for that purpose but quickly becomes awkward as you move away. It is definitely not suited to working with Java or Lisp, or navigating large directories.
Acme is often compared to vi/emacs as a power-user's tool with a different operating paradigm. It is, but I think people wrongly point to the keyboard/mouse issue as the basic difference. The real difference is that vi/emacs are all about configurability but Acme focuses on integration with the system while not being configurable at all (unless you count hacking the source).
Also, the frequent reference to UTF-8 is a bit misleading. Handling Unicode is about more than just recognizing the code points. It is tricky to properly display the various scripts of the world. For a good treatment of the issues presented in a simple interface, look at the Yudit editor.
Finally, I'm kind of surprised at the lack of interest in controlling fonts. My usual coding font is 12 pt. Dina or Terminus. But if my eyes are really tired, I might switch to 16 pt. Monaco. On the other hand, I sometimes use 8 pt. ProFont to better get an overview. I would think even Plan 9 hackers would appreciate being able to quickly shift around like that.
next reply other threads:[~2008-08-20 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 15:12 Wendell xe [this message]
2008-08-20 15:38 ` Tom Lieber
2008-08-20 15:47 ` Robert Raschke
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=384332.12907.qm@web57601.mail.re1.yahoo.com \
--to=wendellxe@yahoo.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).