zsh-users
 help / color / mirror / code / Atom feed
From: Martijn Dekker <martijn@inlv.org>
To: zsh-users@zsh.org
Subject: Re: Opensource.com Zsh article
Date: Wed, 18 Sep 2019 23:37:32 +0100	[thread overview]
Message-ID: <7a681972-e690-a800-306f-182cd686030d@inlv.org> (raw)
In-Reply-To: <a4b9f8e1-ad20-40a0-5da5-2854fb0652a3@eastlink.ca>

Op 18-09-19 om 18:06 schreef Ray Andrews:
> On 2019-09-17 5:39 p.m., TJ Luoma wrote:
>> https://scriptingosx.com/moving-to-zsh/
>
> It astonishes me that the reason for the switch is claimed to be a 
> licensing version detail.

There's nothing astonishing about that. It's been well known for years 
that Apple won't touch the GPLv3 with a ten foot pole. That's why all 
the GNU stuff in macOS is stuck on the last GPLv2 versions, which are 
all really old now, so they're slowly replacing it all.

>   I understand that there's no one left in the 
> cockpit at bash, would that not be a better reason?

What makes you think that? If you read through the bug-bash list it's 
pretty obvious that Chet is still firmly in charge and actively 
developing bash as always. It had a new major 5.0 release fairly 
recently as well, which make it run scripts quite a lot faster.

>   Even now I can't 
> quite accept that something as essential to computing as the shell 
> should be treated so casually.  So it's zsh from now on, but even then 
> all this will rest on the shoulders of our few intrepid volunteers? 

Apple has plenty of in-house manpower and expertise to take over zsh 
development if the need should ever arise. They've done that sort of 
thing before (CUPS comes to mind). Meanwhile perhaps they'll contribute.

- M.

-- 
modernish -- harness the shell
https://github.com/modernish/modernish

  parent reply	other threads:[~2019-09-18 22:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-17 22:29 Bart Schaefer
2019-09-18  0:39 ` TJ Luoma
2019-09-18 16:06   ` Ray Andrews
2019-09-18 16:13     ` Jérémie Roquet
2019-09-18 16:37       ` Ray Andrews
2019-09-18 16:54         ` Daniel Shahaf
2019-09-18 17:05           ` Ray Andrews
2019-09-18 17:17         ` Roman Perepelitsa
2019-09-18 19:23           ` Ray Andrews
2019-09-18 22:37     ` Martijn Dekker [this message]
2019-09-19  1:43       ` Ray Andrews
2019-09-19 16:08         ` Daniel Shahaf
2019-09-19 17:32           ` Ray Andrews
2019-09-19 18:04             ` Daniel Shahaf
2019-09-19 19:40               ` Ray Andrews
2019-09-19 22:33                 ` Daniel Shahaf
2019-09-19 22:59                   ` Bart Schaefer
2019-09-20  0:06                     ` Ray Andrews
2019-09-20  1:01                       ` TJ Luoma
2019-09-20  3:51                         ` Ray Andrews
2019-09-20 13:33                         ` Daniel Shahaf
2019-09-20 13:51                           ` Ray Andrews
2019-09-20 21:51                           ` Bart Schaefer
2019-09-20 22:08                             ` Ray Andrews
2019-09-21  8:21                             ` Daniel Shahaf

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=7a681972-e690-a800-306f-182cd686030d@inlv.org \
    --to=martijn@inlv.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).