← Back to context

Comment by daishi55

2 days ago

It’s just one long ad hominem

I don't think you are using that right. Saying someone is bringing a bad vibe to your project, as the point he has a bad vibe is just stating the conclusion.

Like if someone calls you a bad programmer and doesn't hire you as a programmer, isn't ad hominem

  • No, the discussion started with a the article from Bun, stating that rust has some technical advantages for them. The response from the Zig creator is a bunch of personal attacks directed at one guy, like calling him a stinky manager. All of these are fully unrelated to which language is better for Bun.

    This is like the textbook definition of an ad hominem.

    • Ad Hominem is only a fallacy when the speaker's personal qualities are irrelevant to the topic at hand. When one man has unilateral control over a project, you have to consider it as an extension of their personality.

    • To be pedantic the ad hominem fallacy is about trying to deny an argument by attacking the author, so in a discussion about zig Vs rust if Andrew isn't trying to enter the discussion and just argue "that guy was stinky, glad he is gone" is not really an ad hominem, just not classy let's say.

      2 replies →

    • > This is like the textbook definition of an ad hominem.

      No, it isn't at all. Ad hominem is only in effect and fallacious when the logic turns on the personal attack. "You're wrong because you're stupid" is ad hominem. "You're wrong and also you're stupid" is impolite, but logically fine.

      To clarify, I think that the entire "History" section is unrelated to Andrew's argument, only the "Addressing the Blog Post" section actually contains arguments, and that section doesn't contain the rude comments, it's focused on technical decision-making.

      4 replies →

  • Right I think the correct term is “character assassination”. It starts by calling him a novice, goes on to call him a “stinky manager”, and then lands the deepest cut possible in this profession: his code sucks. At least Kelley thanked him for his money.

    This is not refreshing, I usually expect better from Kelley. The best move would have been to say nothing at all except “best of luck, Zig will miss him but”. Now all Ziglings must wonder if they’re going to receive a hit piece from the Zig founder if they cross him.

    • Do you think that all ziglings refuse to write idiomatic code, have public fights with the language maintainers, and then write giant blog posts about how they're ditching the language because it just isn't good enough?

      2 replies →

  • I think I am using it right. The implication of the whole post is that Jared's technical points about Zig vs Rust aren't valid because he's a bad programmer. The alternative interpretation is that calling Jared a bad programmer is a non-sequitur unrelated to the argument and is included purely out of spite.

    Take your pick I guess, but the way I meant it I was indeed using the term correctly.

Part of it might feel like ad hominem, but I think the bluntness is justified in this case. It provides some pretty important context on the situation.

As an outside observer who knew little about Zig and Bun, the impression I got is that the rewrite came out of nowhere, and that the Zig community was surprised by it. The post makes it quite clear that this wasn't the case, and describes how the actions and overall mentality of Bun's creator already suggested such a thing was likely to happen, straight from the mouth of someone who worked with him and isn't afraid to voice his thoughts. Not everything needs to be PR speak.

  • You can be blunt without being hateful or an asshole. It's not about PR, it's about treating other people as human beings.

It isn't. The grapevine stuff was unnecessary and should have been cut out but there is plenty of concrete stuff in there as well.