From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Compiling Emacs from Source
Date: Wed, 08 Nov 2017 20:21:42 +0100 [thread overview]
Message-ID: <864lq4a855.fsf@zoho.com> (raw)
In-Reply-To: m2tvy4buji.fsf@pandora.lan
Dan Mack wrote:
> My two cents [...] YMMV
If that's your two cents, one sure gets curious
whatever gold bullions must be in your family
safe...
Indeed, compiling from source isn't difficult.
The reason it is an elite/hacker hangup isn't
because of the level of difficulty, rather the
perfectionist/OCB approach. And, some people
actually benefit from it as well :)
In general, compiling an individual piece of
software isn't difficult. The package manager
and their interfaces are 1) a shorthand for
doing it with less effort and with a uniform
interface, which (both) are always welcome; and,
more importantly 2) handle the complexity that
rises when all those software pieces hook
together in different ways - different
versions, the compile order, circular
dependencies, and what have you.
The complexity itself isn't difficult to
understand either. Just try to write any piece
of software, say a small Elisp file that does
some variation of what is already there. OK, so
you write that. "Sweet, I'll just put it on my
lamer web pile so Joe, Fritz, and Ivan Hackers
all over the world can use it." Only it isn't
completely standalone as it needs a one-liner
which you have in another file which has
nothing to do with the first file! So you
factor it out to a library. Now this breaks
both files for anyone not having that library -
yeah, "library", like 2-3 lines of codes!
So you put in a comment "; hey guys, you need
to get this as well" so already an all-but
trivial project starts to tangle up. Guess what
with huge software systems developed for half
a century (soon).
So the complexity is in one sense similar to
compiler optimization. Recurrent values are
factored out, unused variables dropped - so
easy, an idiot can do it. Or at least
understand it. But a computer can do it in
close to zero time and it doesn't matter how
big the project gets, the result will be just
as good as those simple cases are applied again
and again...
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2017-11-08 19:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 22:06 Compiling Emacs from Source Robert Thorpe
2017-11-05 22:43 ` Jean-Christophe Helary
2017-11-07 5:43 ` Kendall Shaw
2017-11-07 23:58 ` Emanuel Berg
2017-11-08 1:01 ` John Mastro
2017-11-08 1:27 ` Emanuel Berg
2017-11-08 4:26 ` Emanuel Berg
2017-11-11 20:45 ` Robert Thorpe
2017-11-08 16:32 ` Dan Mack
2017-11-08 19:21 ` Emanuel Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-27 3:29 Compiling Emacs from source Henri-Paul Indiogine
2010-03-27 5:05 ` Óscar Fuentes
2010-03-27 9:52 ` Peter Dyballa
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=864lq4a855.fsf@zoho.com \
--to=moasen@zoho.com \
--cc=help-gnu-emacs@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).