From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Official plugin manager?
Date: Thu, 2 Jan 2020 12:55:04 +0100 [thread overview]
Message-ID: <CAKc7PVDfPCRKVGxchRCMNZ2f1sEZVARs21A2eKPa1kSh9A1VgQ@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVCqRLFdN-1RBnmkZWcJ7JnyfyE5i5zpVFsD28DUF=5k=Q@mail.gmail.com>
On Thu, 2 Jan 2020 at 12:37, Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
>
> On Thu, 2 Jan 2020 at 12:04, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> > http://xyproblem.info/
> >
> > "Write an official plugin manager" is a solution. You have identified
> > several problems in your mail, so let's talk about those problems and
> > consider all possible solutions to them (not only the one that you
> > hardcoded into the subject line of this thread).
>
> Okay. I think that the one interesting point was the 3rd one. I think
> that it harms Zshell's picture out there by making the following
> thinking common: that you cannot use Zsh without loading a bloated
> framework like Oh My Zsh.
I've decided to slightly elaborate on this without jumping to the Y,
i.e.: to the bundled p-m.
I think that OMZ has a guilt of spreading of such thinking (that you
cannot use Zsh without a framework that's bloated – actually but also
by the impression that is given by what's advertised: "(framework)
with nearly 1,500 contributors", "includes 200+ optional plugins",
etc.). It gives the impression that "if you load OMZ, then all Zsh
complex configuration will be done for you" (by the code from the
*1500* contributors...), which implies that the configuration is so
complex that you cannot get a better outcome on your own, especially
if you're a new user. This basically means that Zsh has to be put down
under the layer of OMZ and best if untouched directly, but instead
relying on "an auto-update tool so that makes it easy to keep up with
the latest updates from the community". Hence the thinking-pattern
problem.
To address this public-image pressure from OMZ:
- something has to be added to Zsh,
- a simple uncover of it: it should allow easier configuration,
- configuration often means: loading a theme and the needed
functionality providers (i.e.: plugins),
thus this converges to the bundled p-m solution.
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org
next prev parent reply other threads:[~2020-01-02 11:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 3:17 Sebastian Gniazdowski
2020-01-02 4:28 ` Eric Cook
2020-01-02 11:03 ` Daniel Shahaf
2020-01-02 11:37 ` Sebastian Gniazdowski
2020-01-02 11:55 ` Sebastian Gniazdowski [this message]
2020-01-02 21:30 ` dana
2020-01-03 0:25 ` Sebastian Gniazdowski
2020-01-03 1:36 ` dana
2020-01-03 2:43 ` Sebastian Gniazdowski
2020-01-03 2:45 ` Bart Schaefer
2020-01-03 3:26 ` dana
2020-01-03 5:13 ` Sebastian Gniazdowski
2020-01-03 15:00 ` Peter Stephenson
2020-01-03 20:48 ` Daniel Shahaf
2020-01-03 21:51 ` Roman Perepelitsa
2020-01-03 22:06 ` Daniel Shahaf
2020-01-03 22:26 ` Bart Schaefer
2020-01-03 22:37 ` Roman Perepelitsa
2020-01-04 0:42 ` dana
2020-01-04 1:06 ` Daniel Shahaf
2020-01-04 15:46 ` Roman Perepelitsa
2020-01-04 16:27 ` Daniel Shahaf
2020-01-04 16:41 ` Roman Perepelitsa
2020-01-04 17:35 ` Daniel Shahaf
2020-01-04 17:42 ` Roman Perepelitsa
2020-01-04 17:11 ` Bart Schaefer
2020-01-05 10:40 ` Oliver Kiddle
2020-01-06 17:47 ` Leah Neukirchen
2020-01-03 11:15 ` Oliver Kiddle
2020-01-04 5:16 ` Sebastian Gniazdowski
2020-01-04 6:00 ` Sebastian Gniazdowski
2020-01-02 12:00 ` Roman Perepelitsa
2020-01-02 12:21 ` Sebastian Gniazdowski
2020-01-02 12:27 ` Roman Perepelitsa
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=CAKc7PVDfPCRKVGxchRCMNZ2f1sEZVARs21A2eKPa1kSh9A1VgQ@mail.gmail.com \
--to=sgniazdowski@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).