From: ludo@gnu.org (Ludovic Courtès)
To: Mike Gerwitz <mtg@gnu.org>
Cc: guix-devel@gnu.org, "Clément Lassieur" <clement@lassieur.org>
Subject: Re: Packaging a free Firefox
Date: Thu, 17 May 2018 13:28:56 +0200 [thread overview]
Message-ID: <878t8i34hz.fsf@gnu.org> (raw)
In-Reply-To: <874lj86fmn.fsf@gnu.org> (Mike Gerwitz's message of "Tue, 15 May 2018 12:35:44 -0400")
Hello Mike,
Mike Gerwitz <mtg@gnu.org> skribis:
> IceCat is based on an old ESR; FF has undergone many substantial changes
> (and rewrites of parts of the system) since then; it's much more
> performant and I've found it to be much more stable over the years.
> (I use IceCat at home and FF at work.)
>
> So when users compare IceCat to "Firefox", they're not likely
> performing a valid comparison, since they're going to use a modern
> version of Firefox.
>
> I think Rubén is working on an ESR upgrade, so maybe users' experiences
> will be a bit better soon.
Oh OK, thanks for explaining, I wasn’t aware of that.
Ludo’.
next prev parent reply other threads:[~2018-05-17 11:29 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 21:06 Packaging a free Firefox Clément Lassieur
2018-05-02 21:10 ` Clément Lassieur
2018-05-03 5:00 ` Nils Gillmann
2018-05-03 5:06 ` Nils Gillmann
2018-05-03 5:09 ` Pierre Neidhardt
2018-05-03 14:29 ` next browser (was: Packaging a free Firefox) Jack Hill
2018-05-03 14:35 ` Pierre Neidhardt
2018-05-03 20:23 ` Jack Hill
2018-05-04 3:36 ` Andy Patterson
2018-05-09 16:45 ` Pierre Neidhardt
[not found] ` <20180510020041.1e8b3956@uwaterloo.ca>
[not found] ` <87d0y3hije.fsf@gmail.com>
2018-05-10 14:04 ` ajpatter
2018-05-10 14:36 ` Pierre Neidhardt
2018-05-11 5:00 ` Andy Patterson
2018-05-19 19:26 ` Pierre Neidhardt
2018-05-24 9:53 ` Ricardo Wurmus
2018-05-24 14:18 ` Pierre Neidhardt
2018-05-24 15:33 ` Ricardo Wurmus
2018-05-24 16:44 ` Pierre Neidhardt
2018-05-24 20:37 ` Ricardo Wurmus
[not found] ` <87bmdnhhu8.fsf@gmail.com>
2018-05-10 14:04 ` ajpatter
2018-05-03 6:06 ` Packaging a free Firefox Chris Marusich
2018-05-03 9:53 ` Pjotr Prins
2018-05-03 10:56 ` Mathieu Othacehe
2018-05-11 14:54 ` Pjotr Prins
2018-05-03 17:59 ` Mike Gerwitz
2018-05-04 14:24 ` Pjotr Prins
2018-05-04 16:07 ` Nils Gillmann
2018-05-04 16:27 ` Mike Gerwitz
2018-05-05 12:26 ` Pjotr Prins
2018-05-15 7:10 ` Pjotr Prins
2018-05-15 8:57 ` Ludovic Courtès
2018-05-15 10:13 ` Gábor Boskovits
2018-05-16 17:27 ` Mark H Weaver
2018-05-15 16:35 ` Mike Gerwitz
2018-05-17 11:28 ` Ludovic Courtès [this message]
2018-05-03 19:07 ` Mark H Weaver
2018-05-03 20:45 ` Clément Lassieur
2018-05-12 13:28 ` Clément Lassieur
2018-05-05 22:06 ` Adonay Felipe Nogueira
2018-05-06 1:24 ` Mike Gerwitz
2018-05-06 6:01 ` Nils Gillmann
2018-05-06 13:58 ` Mike Gerwitz
2018-05-06 16:35 ` Hartmut Goebel
2018-05-06 9:48 ` Hartmut Goebel
2018-05-06 12:53 ` Pjotr Prins
2018-05-16 15:44 ` Katherine Cox-Buday
2018-05-16 16:10 ` Tonton
2018-05-16 17:56 ` Katherine Cox-Buday
2018-05-17 11:34 ` Ludovic Courtès
2018-05-17 13:47 ` Nils Gillmann
2018-05-17 15:10 ` Christopher Lemmer Webber
2018-05-17 15:29 ` Nils Gillmann
2018-05-17 17:57 ` Christopher Lemmer Webber
2018-05-18 4:14 ` Pjotr Prins
2018-05-21 4:58 ` Pjotr Prins
2018-05-21 20:07 ` Mark H Weaver
2018-05-22 4:18 ` Pjotr Prins
2018-05-22 19:05 ` Mark H Weaver
2018-07-31 1:51 ` Pjotr Prins
2018-08-01 0:58 ` Mark H Weaver
2018-05-21 20:09 ` Mark H Weaver
2018-05-22 3:55 ` Alex Vong
2018-05-18 5:19 ` Mike Gerwitz
2018-05-18 4:25 ` Pjotr Prins
2018-05-16 19:07 ` Christopher Lemmer Webber
2018-05-16 19:54 ` Oleg Pykhalov
2018-05-16 20:50 ` Katherine Cox-Buday
2018-05-17 1:26 ` Mark H Weaver
2018-05-17 8:21 ` Thorsten Wilms
2018-05-17 11:36 ` Katherine Cox-Buday
2018-05-06 14:05 ` Mike Gerwitz
2018-05-06 15:32 ` Pjotr Prins
2018-05-06 16:33 ` Hartmut Goebel
2018-05-07 0:36 ` Mike Gerwitz
2018-05-07 6:42 ` jah
2018-05-07 16:30 ` Ludovic Courtès
2018-05-08 8:36 ` Pjotr Prins
2018-05-08 0:06 ` Mark H Weaver
2018-05-08 0:20 ` Mark H Weaver
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=878t8i34hz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=clement@lassieur.org \
--cc=guix-devel@gnu.org \
--cc=mtg@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.