unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Barry Warsaw <barry@python.org>
Cc: emacs-devel@gnu.org
Subject: Re: Time to drop the pre-dump phase in the build?
Date: Fri, 10 Jan 2014 16:06:46 -0500	[thread overview]
Message-ID: <20140110160646.1fc16d9f@anarchist.wooz.org> (raw)
In-Reply-To: <83a9f3bmw0.fsf@gnu.org>

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

On Jan 10, 2014, at 10:30 PM, Eli Zaretskii wrote:

>> Interestingly enough albeit tangential, I haven't even byte-compiled my
>> personal elisp files in *decades*.  I just load them from source
>
>Did you measure performance?  Byte-compiled code is about 2 times
>faster.

Not really, but two trends make it not really worth it:

1) Computers are so much more insanely faster now than when I started with
Emacs, or even started vc'ing my personal elisp.

2) More and more of my personal hacks have been subsumed by standard Emacs
functionality that I'm really down to just a few handful of files now.

>> Performance (startup or runtime) hasn't been a problem since I made
>> the switch.
>
>If you are used to slightly slower operation, you will in time stop
>paying attention to the slow-down.  E.g., I run an unoptimized build
>of Emacs most of the time (due to better debugging opportunities), and
>think it is fast enough -- until I fire up an optimized build and am
>amazed by its speed.

Fast enough is good enough. :)

-Barry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-01-10 21:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 19:15 Time to drop the pre-dump phase in the build? Eric S. Raymond
2014-01-10 19:49 ` Eli Zaretskii
2014-01-11  6:16   ` Paul Eggert
2014-01-11  7:17   ` Richard Stallman
2014-01-12  0:16     ` Nix
2014-01-12  3:48       ` Eli Zaretskii
2014-01-12  3:53         ` Eric S. Raymond
2014-01-11  7:17   ` Richard Stallman
2014-01-10 19:51 ` Stefan Monnier
2014-01-10 20:09   ` Eric S. Raymond
2014-01-10 20:13   ` Eli Zaretskii
2014-01-10 20:20 ` Barry Warsaw
2014-01-10 20:30   ` Eli Zaretskii
2014-01-10 21:06     ` Barry Warsaw [this message]
2014-01-10 22:19 ` Daniel Colascione
2014-01-10 22:58   ` David Kastrup
2014-01-11  0:05     ` Daniel Colascione
2014-01-10 23:23   ` Stefan Monnier
2014-01-11  0:07     ` Daniel Colascione
2014-01-11  2:58       ` Stefan Monnier
2014-01-11  3:37         ` Daniel Colascione
2014-01-11  5:13           ` Stefan Monnier
2014-01-11  5:30             ` Daniel Colascione
2014-01-11 16:14           ` Stephen J. Turnbull
2014-01-11 20:13     ` Glenn Morris

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=20140110160646.1fc16d9f@anarchist.wooz.org \
    --to=barry@python.org \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).