all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: Daniele Nicolodi <daniele@grinta.net>
Cc: emacs-devel@gnu.org
Subject: Re: Why fido, icycles, ido, icomplete
Date: Wed, 6 Nov 2019 23:27:40 +0100	[thread overview]
Message-ID: <20191106222740.kz6wqmyoaile25te@Ergus> (raw)
In-Reply-To: <62749f7e-818f-90c8-2792-933aa0de996a@grinta.net>

On Wed, Nov 06, 2019 at 02:30:31PM -0700, Daniele Nicolodi wrote:
>Hello Ergus,
>
>On 06-11-2019 14:20, Ergus wrote:
>> 90% of the emacs users are actually using ivy or helm...
>how do you come to this estimate? I don't think it is something you can
>derive solely from download statistics.
>
>Thank you.
>
>Cheers,
>Daniele
>

Hi Daniele:

When I started using emacs I was very confused about what to use for
completion, so I checked: download statistics and github starts (now
there is the package "paradox" to get that information in the package
manager).

But also the community size of spacemacs (with 188000 starts and 4600
forks) compared to vanilla emacs and a Spanish telegram group for emacs
(197 members now) and a reddit thread related (I can't find it now).

I actually told 90% to be conservative; because 100% of the comments I
have seen related to completion use helm or ivy exclusively. The few
people I knew were using ido 3 years ago (due to the performance issues
in helm) have moved to ivy now.

On the other hand, in my work there is a user who use emacs without any
config at all (because it is in a common server), so as I suppose there
are other people in the same situation I keep that 10% for them. But I
don't think he will be annoyed by an improvement like setting a better
completion by default.

In any case the key of my mail was more about why to maintain so many
alternatives (it is hard to maintain, confusing for the user, complex to
find information (at least in the package manager there is a description
so the user can discover packages there)) and add another one instead of
decide for the best we have and maintain and improve it as much as
possible. Or provide lower level api functionalities for the popular
packages (like ivy), move the others (like ido) to elpa and keep in
built-in emacs only the minimal.

Best,
Ergus



  reply	other threads:[~2019-11-06 22:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191106212018.cnddqzlo5rpdhi6s.ref@Ergus>
2019-11-06 21:20 ` Why fido, icycles, ido, icomplete Ergus
2019-11-06 21:30   ` Daniele Nicolodi
2019-11-06 22:27     ` Ergus [this message]
2019-11-06 22:03   ` João Távora
2019-11-06 22:39     ` Óscar Fuentes
2019-11-06 22:57       ` João Távora
2019-11-06 23:07         ` Óscar Fuentes
2019-11-07  0:36           ` João Távora
2019-11-07  1:07             ` Óscar Fuentes
2019-11-07  1:21               ` Ergus
2019-11-07  1:51                 ` Óscar Fuentes
2019-11-07 10:09               ` João Távora
2019-11-07 18:50                 ` Óscar Fuentes
2019-11-06 23:21     ` Ergus
2019-11-06 23:59       ` Óscar Fuentes
2019-11-07  0:47         ` Ergus
2019-11-07  2:20           ` Óscar Fuentes
2019-11-07  4:59             ` Ergus
2019-11-07 18:26               ` Óscar Fuentes
2019-11-07 14:09             ` Stefan Monnier
2019-11-07 20:35               ` Óscar Fuentes
2019-11-07 21:11                 ` Stefan Monnier
2019-11-07 22:18                   ` Óscar Fuentes
2019-11-07 22:30                     ` Stefan Monnier
2019-11-07 22:34                     ` João Távora
2019-11-07  0:27       ` João Távora
2019-11-07  1:09         ` Ergus
2019-11-07 10:39           ` João Távora
2019-11-07 15:00             ` Ergus
2019-11-08 17:54     ` Filipp Gunbin
2019-11-08 18:10       ` Óscar Fuentes
2019-11-08 18:45       ` Nicolas Semrau
2019-11-08 19:12       ` Eli Zaretskii
2019-11-08 21:31         ` Juanma Barranquero
2019-11-08 22:54           ` João Távora
2019-11-08 23:11             ` Ergus

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=20191106222740.kz6wqmyoaile25te@Ergus \
    --to=spacibba@aol.com \
    --cc=daniele@grinta.net \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.