unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Bloat in the Emacs Windows package
Date: Fri, 19 Apr 2019 01:12:15 +0200	[thread overview]
Message-ID: <87y346rjqo.fsf@telefonica.net> (raw)
In-Reply-To: 87a7gnypsx.fsf@russet.org.uk

phillip.lord@russet.org.uk (Phillip Lord) writes:

> To summarise my feelings about the thread so far:
>
>  - I think most normal users don't need debug symbols,

I agree.

>    so I would be
>    minded to remove them (or not put them). I don't know why I have
>    added "-g3" to the default options. People who know what to do with
>    debug symbols are likely to be able to build Emacs for
>    themselves.

Not really. Building Emacs is much harder than installing gdb, execute
emacs under gdb and obtain an stack trace.

Debug symbols are useful, and that is the reason why GNU/Linux
distributions offer them as a separate package.

>  - We currently install emacs.exe and emacs-26.2.exe. I think we should
>    continue doing this because it is how we do it on other
>    platforms.

As explained on a previous post, IMO the reasoning behind that practice
makes little sense for Windows.

>    The disk space requirement is small (and will be smaller if we
>    remove debug symbols). It probably adds little to the download
>    bandwith (because of zip) and will add nothing with the .exe
>    installer for Emacs-27. And NTFS compression fixes the problem (and
>    more) for those who really care about space (and they are probably
>    using it already).

Creating symlinks on Windows (pre-10, IIRC) require administrator
privileges. Ditto for enabling NTFS compression.

About what is small and what isn't: that's a personal opinion. I'm mildly
annoyed about the fact that yesterday's MB are today's GB, without a
proportional increase in functionality. Also, I recently started using
an Android tablet with 32 GB storage and I really appreciate how the
Termux guys manage to produce packages that are significantly smaller
than those on desktop GNU/Linux. There are low-end computers in stores
with 32 GB SSDs. And people use old hardware too.

> I am happy to be corrected here if I am missing some unintended
> consequence, or if you disagree with my justifications.
>
>
> Unanswered questions for me:
>
>  - If we remove debug symbols, why not do -O3 which may produce some
>    performance benefit?

-O3 does not necessarily mean better performance. My bet is that the
difference will be insignificant for Emacs. I've seen plenty of cases
where -O3 was measurably worse than -O2.




  reply	other threads:[~2019-04-18 23:12 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17  5:01 Bloat in the Emacs Windows package Björn Lindqvist
2019-04-17  7:31 ` Eli Zaretskii
2019-04-17 11:15   ` Van L
2019-04-17 11:26     ` Eli Zaretskii
2019-04-17 12:39   ` Stefan Monnier
2019-04-17 14:49     ` Eli Zaretskii
2019-04-17 16:17       ` Eli Zaretskii
2019-04-18 22:02         ` Björn Lindqvist
2019-04-19  7:00           ` Eli Zaretskii
2019-04-17 17:26     ` Phillip Lord
2019-04-17 17:55       ` Stefan Monnier
2019-04-19  0:02       ` Björn Lindqvist
2019-04-19  7:33         ` Eli Zaretskii
2019-04-19 13:23           ` Óscar Fuentes
2019-04-22 21:04             ` Phillip Lord
2019-04-22 21:41               ` Óscar Fuentes
2019-04-17 13:42   ` Stefan Monnier
2019-04-17 16:19     ` Óscar Fuentes
2019-04-17 17:28     ` Phillip Lord
2019-04-17 15:07   ` Björn Lindqvist
2019-04-17 16:32     ` Eli Zaretskii
2019-04-18 23:44       ` Björn Lindqvist
2019-04-19  7:27         ` Eli Zaretskii
2019-04-19 14:17           ` Óscar Fuentes
2019-04-19 15:05             ` Eli Zaretskii
2019-04-22 20:55             ` Phillip Lord
2019-04-17 17:39     ` Phillip Lord
2019-04-17 18:06       ` Stefan Monnier
2019-04-17 18:32       ` Eli Zaretskii
2019-04-18 16:05         ` Phillip Lord
2019-04-18 19:08           ` Eli Zaretskii
2019-04-18 21:19             ` Phillip Lord
2019-04-18 23:12               ` Óscar Fuentes [this message]
2019-04-19  6:29               ` Eli Zaretskii
2019-04-22 20:40                 ` Phillip Lord
2019-04-23  2:25                   ` Stefan Monnier
2019-04-23 10:01                     ` Phillip Lord
2019-04-23 11:28                       ` Robert Pluim
2019-04-23 21:49                         ` Phillip Lord
2019-04-26 16:30                       ` Phillip Lord
2019-04-26 17:04                         ` Óscar Fuentes
2019-04-26 21:41                           ` Phillip Lord
2019-04-27 18:12                         ` Björn Lindqvist
2019-04-27 18:17                           ` Phillip Lord
2019-05-03  1:06                             ` Björn Lindqvist
2019-05-03  6:49                               ` Eli Zaretskii
2019-05-03 18:38                                 ` Björn Lindqvist
2019-05-03 18:42                                   ` Eli Zaretskii
2019-05-03 20:20                                     ` Stefan Monnier
2019-04-23  5:37                   ` Eli Zaretskii
2019-04-17 15:44 ` Phillip Lord
2019-04-17 16:25   ` Óscar Fuentes
2019-04-17 16:46     ` Eli Zaretskii
2019-04-18 16:00       ` Phillip Lord
2019-04-18 15:56     ` Phillip Lord
2019-04-18 16:39       ` Óscar Fuentes

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=87y346rjqo.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --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).