zsh-users
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Marc Chantreux <eiro@phear.org>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: about founding z developement of zsh
Date: Thu, 21 Jun 2018 23:44:04 +0200	[thread overview]
Message-ID: <CAKc7PVC-AVeRMNtm3iM0OpGYOuG6yB4j7kv00a_EWhiPDYFbAw@mail.gmail.com> (raw)
In-Reply-To: <20180619091217.GC8263@prometheus.u-strasbg.fr>

On 19 June 2018 at 11:12, Marc Chantreux <eiro@phear.org> wrote:
> hello people,
>
>> The problem with that is none of the core zsh developers have
>> ever asked for contributions in a quarter century of its existence,
>> and all are unpaid volunteers.
>
> well ... i am a zsh user since circa 2001 and always felt i didn't gave
> zsh enough (same for perl, vim, linux, dwm, gnome and all those awesome
> software that gave me 20 years of fun using floss).
>
> i only have 1 patch in zsh, i don't really contribute to zsh but i try
> to be active in the ecosystem
>
> * support french users
> * promote zsh in technical mailing lists, local meetups and
>   other conferences
>   (http://act.perlconference.org/tpc-2018-glasgow/talk/7338)
> * start writing a zsh programming guide
>   (https://github.com/eiro/zsh-programming-guide)
> * start writing a plugin system with a very opiniated coding style
>   (as perlish as we can) (https://github.com/zsh-uze)
>
> basically, i try to spend some of the time i spared using zsh to promote
> it because ... gosh ... when i have to read some bash/ksh/sh/posix code,
> my eyes are bleeding and i really want to see more zsh outzere.
>
> i started a list of things i would like to see appearing in zsh here
>
>     https://github.com/eiro/zsh-programming-guide/blob/master/c/wishlist.md
>
> and i guess some topics means huge work so unpaid patches coming time to
> time are not enough.
>
> and i wonder if this is worth a founding campain... and to be honnest,
> sometimes i also wonder if a fresh start using a modern langage (like crystal or rust)
> should be an option. there is the elvish shell

I think that fresh start is a heavy thing, I recall Linus once said
"creating by destroying first". I'm not sure if the message that
"fresh start" conveys it's actually this, to turn away from current
Zsh, i.e. "destroy" (heavy word, but the discussion Linus had, maybe
even about "rewriting in C++", was little emotional). To then engage
into heritage-free coding in something that is placed as opposite to
C.

I think different approach is maybe possible. Rust allows gradual
rewrite, there's a project gradually rewriting Emacs (Wilfred/remacs).
If this would be started, then – one association comes to my mind: it
would be like in many Anime/Manga, where characters change form, but
keep their identity, and also essential traits (new form still
expresses character's main properties). ;)

Zsh would keep its identity, it would be just expressed in a fresh
form. I think this would be good to many people, to act again like
when e.g. new completion system was coded (I assume it took some time
and there was some mobilization to quickly have better product than
the previous completion system).

-- 
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin


  parent reply	other threads:[~2018-06-21 21:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 16:55 3 years of coding Zsh Sebastian Gniazdowski
2018-06-15 17:29 ` Ray Andrews
2018-06-15 22:49   ` Jason L Tibbitts III
2018-06-17 12:41   ` Sebastian Gniazdowski
2018-06-17 14:21     ` Daniel Shahaf
2018-06-17 14:43       ` Sebastian Gniazdowski
2018-06-18 15:00         ` Peter Stephenson
2018-06-19  7:34           ` Sebastian Gniazdowski
2018-06-19  8:27             ` Peter Stephenson
2018-06-19  9:12           ` about founding z developement of zsh Marc Chantreux
2018-06-20 10:19             ` René Wilhelm
2018-06-20 11:02               ` Marc Chantreux
2018-06-21 21:44             ` Sebastian Gniazdowski [this message]
2018-06-17 17:39       ` 3 years of coding Zsh Ray Andrews

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=CAKc7PVC-AVeRMNtm3iM0OpGYOuG6yB4j7kv00a_EWhiPDYFbAw@mail.gmail.com \
    --to=sgniazdowski@gmail.com \
    --cc=eiro@phear.org \
    --cc=zsh-users@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).