zsh-users
 help / color / mirror / code / Atom feed
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Opensource.com Zsh article
Date: Wed, 18 Sep 2019 19:17:15 +0200	[thread overview]
Message-ID: <CAN=4vMoLgbMdTJaQ+YCLg=Z110chkeuL1oV6J6jxksq7Rohh-g@mail.gmail.com> (raw)
In-Reply-To: <2369b204-5afc-d523-c713-acf64e153a3f@eastlink.ca>

On Wed, Sep 18, 2019 at 6:38 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> 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.

This does happen. Google has dedicated teams with dozens of engineers
working on Linux and LLVM. Bram Moolenaar is still working on vim and
getting paid to do so. It just so happens that neither bash nor zsh
are mission-critical for large companies. The fact that zsh is
replacing bash as the default shell on macOS will go unnoticed for the
laymen and experts alike. The former either don't use shell or won't
notice the difference; the latter know how to install their shell of
choice. There may be bugs in bash and zsh due to underfunding but
these are much harder to exploit than bugs in the kernel or javascript
engine.

It's not necessarily fair that some open-source contributors get to
enjoy working on their favorite project and getting paid to do it
while others have to fund this activity from their own pocket despite
having as much if not bigger impact on the world. My point is that
large corporations aren't acting irrationally. They generally allocate
engineering resources where the payoff is the highest. If no one is
sponsoring bash and zsh, it's because paid engineers' time (a scarce
and expensive commodity!) generates higher yield elsewhere.

One could argue that the benefits of a better shell accrue to everyone
while funding has to come from the pocket of a single company when the
funding decision is made. So we have a sort of the tragedy of the
commons. This argument is getting weaker by the day when a handful of
the largest tech companies eats an increasingly larger share of the
world economy. Google, Apple, Microsoft or Amazon can certainly afford
to spend money open source projects that make everyone better off. And
they do, roughly according to the marginal benefit-per-dollar-spent.

Roman.

  parent reply	other threads:[~2019-09-18 17:18 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 [this message]
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='CAN=4vMoLgbMdTJaQ+YCLg=Z110chkeuL1oV6J6jxksq7Rohh-g@mail.gmail.com' \
    --to=roman.perepelitsa@gmail.com \
    --cc=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).