4 ms·

> This post is not here to ascribe any intention to Zig proponents, especially the leadership and employees of the Zig Software Foundation. I did that once, and

> This post is not here to ascribe any intention to Zig proponents, especially the leadership and employees of the Zig Software Foundation. I did that once, and I regret it. Where is such blog post?

vanderZwan 5y ago
Maybe we should respect his implied wishes to not go there again, since he's clearly trying his best for this blog post to be useful constructive critique?
- richardfey 5y ago
  I can appreciate two posts written in two different ways by the same person and be longing to see the difference.
  - vanderZwan 5y ago
    That's not the point.
    - richardfey 5y ago
      What point? It's the reason why I asked. You were implying I want to read the other post to judge the author, I am explaining that it didn't even cross my mind and I am miles away from that intention.
      - vanderZwan 5y ago
        I didn't imply anything about you, I just reminded you that it is the author's wish that we don't dig that up. I see no reason to not respect that request
tingletech 5y ago
maybe this one https://gavinhoward.com/2021/02/rust-zig-and-the-futility-of-replacing-c/ https://gavinhoward.com/2021/02/rust-zig-and-the-futility-of...
- exikyut 5y ago
  That article mostly calls out some Rust-vs-C comparison points about a specific Python library that were honestly reasonably interesting to read. The Zig part has a number of updates and clarifications that contribute helpful balance while not disrupting the original text. Quite a few of the points have ended up being superceded by developments and evolution in the language.
gavinhoward 5y ago
Author here. It was discussion on lobste.rs, not a blog post. I would rather not link to it because I'm not proud of what I did. But you could find it if you try.
- richardfey 5y ago
  Ok, thanks for the clarification! I won't but at the same time I think everyone can make mistakes, despite the unforgiving nature of written digital records.

> This post is not here to ascribe any intention to Zig proponents, especially the leadership and employees of the Zig Software Foundation. I did that once, and I regret it. Where is such blog post?

vanderZwan 5y ago

Maybe we should respect his implied wishes to not go there again, since he's clearly trying his best for this blog post to be useful constructive critique?

richardfey 5y ago
I can appreciate two posts written in two different ways by the same person and be longing to see the difference.
- vanderZwan 5y ago
  That's not the point.
  - richardfey 5y ago
    What point? It's the reason why I asked. You were implying I want to read the other post to judge the author, I am explaining that it didn't even cross my mind and I am miles away from that intention.
    - vanderZwan 5y ago
      I didn't imply anything about you, I just reminded you that it is the author's wish that we don't dig that up. I see no reason to not respect that request

tingletech 5y ago

maybe this one https://gavinhoward.com/2021/02/rust-zig-and-the-futility-of-replacing-c/ https://gavinhoward.com/2021/02/rust-zig-and-the-futility-of...

exikyut 5y ago
That article mostly calls out some Rust-vs-C comparison points about a specific Python library that were honestly reasonably interesting to read. The Zig part has a number of updates and clarifications that contribute helpful balance while not disrupting the original text. Quite a few of the points have ended up being superceded by developments and evolution in the language.

gavinhoward 5y ago

Author here. It was discussion on lobste.rs, not a blog post. I would rather not link to it because I'm not proud of what I did. But you could find it if you try.

richardfey 5y ago
Ok, thanks for the clarification! I won't but at the same time I think everyone can make mistakes, despite the unforgiving nature of written digital records.