From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Opensource.com Zsh article
Date: Wed, 18 Sep 2019 09:37:23 -0700 [thread overview]
Message-ID: <2369b204-5afc-d523-c713-acf64e153a3f@eastlink.ca> (raw)
In-Reply-To: <CAFOazAPD87azQ2QTgBAKZjCk+DUs8gue4G-LRFNute7XWAR5jA@mail.gmail.com>
On 2019-09-18 9:13 a.m., Jérémie Roquet wrote:
>
> It's kind of what happens with other critical pieces of
> infrastructure, like gnupg and openssl, unfortunately…
>
So I've heard. I have no direct experience of any of that tho. You'd
think that with Linux being so central to so many things now that
there'd be some sort of consortium of companies and governments and
universities to look after the essential software, even to pay the key
people. Imagine Peter and Bart, etc. getting a dollar an hour for their
work vs. flat nothing. Linus himself is payed. And I wonder about the
next generation. When was the last time a new recruit learned how zsh
works down in the engine room?
next prev parent reply other threads:[~2019-09-18 16: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 [this message]
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
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=2369b204-5afc-d523-c713-acf64e153a3f@eastlink.ca \
--to=rayandrews@eastlink.ca \
--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).