zsh-users
 help / color / mirror / code / Atom feed
From: "Mark J. Reed" <markjreed@gmail.com>
To: zsh-users@zsh.org
Subject: Re: Why would I use .namespace.myvar?
Date: Sun, 10 Mar 2024 19:53:05 -0400	[thread overview]
Message-ID: <CAA=-s3yLDG53s-Vn1yHKmLj8hPB77U-b_ijsxg95v6-+hdLbXQ@mail.gmail.com> (raw)
In-Reply-To: <2e33aeab-865a-48cc-8f31-4916d4a0c604@eastlink.ca>

[-- Attachment #1: Type: text/plain, Size: 2220 bytes --]

On Sun, Mar 10, 2024, at 6:16 PM, Ray Andrews wrote:

>  BTW interesting to learn that ksh is still in active development, I
> thought it was on
>  ice, like bash.


Around twenty years ago, AT&T moved ownership of ksh to their open source
arm, the AT&T Software Technology group (AST), which maintained it as an
open project on GitHub. As with prior releases, the year of the major
release (and corresponding edition of the book) was kept as the "major
revision" number, while subsequent releases incremented an alphabetic
suffix. The last AST release was 93u, released in December 2012 - the 23rd
release of the 1993 version of ksh.  After that the codebase was dormant
for a while.  Then in 2019 a developer got excited about reviving the
project and updating it. They started with the in-progress incomplete 93v
release, which they called "93v-", but the result was dubbed "ksh 2020".
2020 had some bug fixes and improvements, but the code changes were
substantial, performance suffered, there was a lot of drama on the project.
I saw accusations that the new developer was hacking and slashing the
codebase without taking the time to understand it or listen to those who
did. I wasn't paying enough attention to know how valid the criticism was,
but the drama seems to have been enough to torpedo the project. However, if
you run "brew install ksh93" on macOS, 2020.0 is what you get to this day.

Then some of the 2020 contributors decided to start over from the AT&T
source code, backporting the bug fixes from ksh2020 onto the
last-known-stable 93u, and building up from there. Their approach is to
tread carefully and not do anything drastic.  That effort has given us the
ksh93u+X/1.x.y versions, most recently ksh93u+m/1.0.8 at the end of last
year; 1.1.0 is expected soon.

The GNU folks haven't been idle, though. The latest official bash release
is 5.2, from 2022, but the patchlevel is up to 5.2.26, and there have been
commits as recently as this week on the devel branch.

There are still at least bugfixes going into ash and dash (and busybox,
whose sh is based on ash), too. So yeah, Zsh is far from the only
Bourne-family shell still seeing active development.

--
Mark J. Reed <markjreed@gmail.com>

[-- Attachment #2: Type: text/html, Size: 3067 bytes --]

  reply	other threads:[~2024-03-10 23:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-09 14:30 Stephane Chazelas
2024-03-09 22:58 ` Bart Schaefer
2024-03-10 12:13   ` Stephane Chazelas
2024-03-10 20:08     ` Bart Schaefer
2024-03-10 22:16       ` Ray Andrews
2024-03-10 22:45         ` Lawrence Velázquez
2024-03-10 23:02           ` Ray Andrews
2024-03-10 23:53             ` Mark J. Reed [this message]
2024-03-11  2:22               ` Ray Andrews
2024-03-11  2:35                 ` Bart Schaefer
2024-03-11  2:50                   ` Ray Andrews
2024-03-11  7:53               ` Stephane Chazelas
2024-03-10 22:48         ` Bart Schaefer
2024-03-10 23:14           ` 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='CAA=-s3yLDG53s-Vn1yHKmLj8hPB77U-b_ijsxg95v6-+hdLbXQ@mail.gmail.com' \
    --to=markjreed@gmail.com \
    --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).