public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: LIU Hao <lh_mouse@126.com>
To: Dave Blanchard <dave@killthe.net>, gcc@gcc.gnu.org
Subject: Re: GNU = Junkware
Date: Sun, 27 Nov 2022 22:53:52 +0800	[thread overview]
Message-ID: <94a5eb92-9273-28da-a7a0-b671916c023c@126.com> (raw)
In-Reply-To: <20221126032052.2f32ed2af88309edd76aa262@killthe.net>


[-- Attachment #1.1: Type: text/plain, Size: 1347 bytes --]

在 2022-11-26 17:20, Dave Blanchard 写道:
> No, I'm not trolling, just venting here for a moment. So sick of garbage ass, crusty junkware that's always a battle to the death to accomplish anything.
> 
> I really understand where Liu Hao was coming from yesterday when he was in here raging against the AT&T assembler. I could sense the bitterness and disgust in him, the kind that can only come from a lifetime of bitter disappointment in the status quo. It's like he's just as sick and tired as I am of broken ass, buggy software.
> 
> GNU GCC/GLIBC IS THE MOST PAINFUL PIECE OF SHIT FUCKING SOFTWARE ON THE PLANET TO BOOTSTRAP.
> 
>

Although the AT&T syntax is stupid, for people who don't write assembly, such stupidity can be 
pretended to not exist at all; that's what 'indirection' is for.

You may have a strong dislike for something, but that doesn't make it 'junkware'. (And GCC is 
actually great; it's even greater if others can keep it deviating from official documentation, but 
still working well!) No matter what piece of software you take a look into, there's always something 
fundamentally carved into its cornerstone, which can never be got rid of. It's what always happens 
and always will. It's very very universal. So, stop that. GCC doesn't deserve your disrespect.



-- 
Best regards,
LIU Hao


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

      parent reply	other threads:[~2022-11-27 14:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-26  9:20 Dave Blanchard
2022-11-26 10:41 ` Jonathan Wakely
2022-11-26 14:24 ` Paul Smith
2022-11-26 16:15 ` Paul Koning
2022-11-27 14:53 ` LIU Hao [this message]

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=94a5eb92-9273-28da-a7a0-b671916c023c@126.com \
    --to=lh_mouse@126.com \
    --cc=dave@killthe.net \
    --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).