emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Ken Mankoff <mankoff@gmail.com>
Cc: Max Nikulin <manikulin@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Org links and Flatpak firefox
Date: Sat, 30 Jul 2022 13:49:40 +1000	[thread overview]
Message-ID: <8635ej45he.fsf@gmail.com> (raw)
In-Reply-To: <87a68s2474.fsf@t480.home>


Ken Mankoff <mankoff@gmail.com> writes:

>
>> Out of curiosity, what is the reason why you are avoiding firefox as a
>> snap package?
>
> I'm not 100 % sure why but I don't like snap. Maybe because it pollutes the home folder. I
> read up on snap vs flatpak vs AppImage and flatpak seemed to get the best reviews, so I've
> gone with that one.
>

There has been a real issue with startup times for snap based
firefox. While there have been some improvements very recently, the snap
version is still significantly slower to start than the flatpak version
(on my system, it was taking over 25 seconds! This is on a 20 core i7
with 32Gb RAM and SSD).

I recently switched from Ubuntu (which favours snap) to Fedora (which
favours flatpak). However, when I was on Ubuntu, I actually replaced the
snap version with the deb version (this is still possible, but people
don't necessarily know that) because it was so much faster to start. I
think the deb/rpm based versions are still the fastest, but flatpak
opens firefox within just a couple of seconds on the same hardware where
snap took 25.


      reply	other threads:[~2022-07-30  3:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-02 16:03 Org links and Flatpak firefox Ken Mankoff
2022-07-02 23:10 ` Tim Cross
2022-07-03  3:46 ` Max Nikulin
2022-07-03 13:25   ` Ken Mankoff
2022-07-05 15:16     ` Max Nikulin
2022-07-28 23:41       ` Ken Mankoff
2022-07-30  3:49         ` Tim Cross [this message]

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8635ej45he.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.com \
    --cc=mankoff@gmail.com \
    /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/org-mode.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).