public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Barry Manilowa <joebeazelman@gmail.com>
To: gcc@gcc.gnu.org
Subject: Why does filing a bug report have to be so damn hard?
Date: Thu, 15 Dec 2022 01:28:13 -0500	[thread overview]
Message-ID: <CAG53Cr8wsDvQqQZUSdac0YeWd-cymCQOoKBhhVjPEHfHJfGnDQ@mail.gmail.com> (raw)

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

Seriously? You UNIX folks are completely clueless about usability! It would
have been far easier to supply a built-in or separate utility to
automatically collect all the pertinent source files with the option of
mailing them to you. It also wouldn't be half as backward if you didn't
make me read a tome's worth of hostile verbiage telling me what you want
and don't want while wading through irrelevant instructions with
hyperlinking hell because you can't be bothered with the effort of
separating the different programming languages.

If you UNIX folks could have it your way, we'd all still be typing on
teleprinters and staring at green monitors getting carpal tunnel syndrome
because you can't be bothered with usability. Let me remind you that it was
Apple, the evil proprietary monster, who had the consideration to make
their products usable by people with disabilities. Their biggest mistake
was to adopt UNIX, which would've been the biggest productivity-killing
malware ever created if it wasn't for Git.

             reply	other threads:[~2022-12-15  6:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15  6:28 Barry Manilowa [this message]
2022-12-15 18:07 ` Paul Smith

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=CAG53Cr8wsDvQqQZUSdac0YeWd-cymCQOoKBhhVjPEHfHJfGnDQ@mail.gmail.com \
    --to=joebeazelman@gmail.com \
    --cc=gcc@gcc.gnu.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).