From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Cc: Daniel Shahaf <d.s@daniel.shahaf.name>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: A serious bug in execution – where to debug?
Date: Wed, 31 Jul 2019 16:11:21 +0200 [thread overview]
Message-ID: <CAN=4vMq_LtNmr+_W3UvCU02rH7CN4vkqthGd6YN86M_BgfE9RA@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVBO2Ry8Q9ET8K_UMUL175G9iOzzzosriGxWMtNw_hDX=A@mail.gmail.com>
On Wed, Jul 31, 2019 at 3:40 PM Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
>
> On Wed, 31 Jul 2019 at 15:34, Roman Perepelitsa
> <roman.perepelitsa@gmail.com> wrote:
> > a feature. It's disrespectful to the developers whose code is
> > brutalized, and it causes extra strain on them due to bug reports by
> > the affected users.
>
> I see. For me the topic isn't associated with brutalization. It's a
> removal of plugin's widget together with its binding, so that it's not
> exposed anymore. A simple withdrawal of plugin's presence.
Once upon a time there lived Jack -- the sole designer and
manufacturer of TV sets that bore his name. He took pride in the
functional and aesthetic properties of his product. Jack TVs had a
slick screen that looked almost weightless, and a nice remote for
turning the TV on and off. Then one day an enterprising distributor
showed up in town and started bundling Jack TV together with other
home appliances and advertising rocks as a general tool for turning
off electronic devices. "It often works", he said. Jack shook his head
every time he saw a scratched or broken screen with his name on the
frame. He no longer told people he made those TVs as it became
difficult to look at the brutalized hunks of steel and glass with
pride. "I'm not brutalizing this TV set, I'm just throwing rocks at
it", one customer was heard to say. He didn't know there was a remote.
The distributor didn't tell him.
Roman.
next prev parent reply other threads:[~2019-07-31 14:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 17:00 Sebastian Gniazdowski
2019-07-30 17:05 ` Sebastian Gniazdowski
2019-07-30 17:41 ` Roman Perepelitsa
2019-07-30 17:55 ` Sebastian Gniazdowski
2019-07-30 18:12 ` Roman Perepelitsa
2019-07-30 18:16 ` Sebastian Gniazdowski
2019-07-30 18:22 ` Roman Perepelitsa
2019-07-30 18:53 ` Sebastian Gniazdowski
2019-07-30 19:23 ` Roman Perepelitsa
2019-07-30 19:34 ` Sebastian Gniazdowski
2019-07-30 19:41 ` Roman Perepelitsa
2019-07-30 19:59 ` Sebastian Gniazdowski
2019-07-30 20:08 ` Roman Perepelitsa
2019-07-30 20:38 ` Sebastian Gniazdowski
2019-07-30 18:27 ` Bart Schaefer
2019-07-30 18:46 ` Sebastian Gniazdowski
2019-07-30 21:02 ` Roman Perepelitsa
2019-07-30 21:38 ` Sebastian Gniazdowski
2019-07-30 21:45 ` Roman Perepelitsa
2019-07-30 21:54 ` Sebastian Gniazdowski
2019-07-30 22:11 ` Roman Perepelitsa
2019-07-30 22:18 ` Daniel Shahaf
2019-07-30 22:32 ` Roman Perepelitsa
2019-07-31 1:30 ` Sebastian Gniazdowski
2019-07-31 7:23 ` Roman Perepelitsa
2019-07-31 11:41 ` Sebastian Gniazdowski
2019-07-31 12:40 ` Roman Perepelitsa
2019-07-31 13:10 ` Sebastian Gniazdowski
2019-07-31 13:34 ` Roman Perepelitsa
2019-07-31 13:40 ` Sebastian Gniazdowski
2019-07-31 14:11 ` Roman Perepelitsa [this message]
2019-07-31 17:56 ` Sebastian Gniazdowski
2019-07-31 1:42 ` Bart Schaefer
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=4vMq_LtNmr+_W3UvCU02rH7CN4vkqthGd6YN86M_BgfE9RA@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=sgniazdowski@gmail.com \
--cc=zsh-workers@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).