3 ms·

Yet we see this harassment continuing on this thread. The article I linked is just a drop in the ocean. Nitpicking over leaking bytes and language features eve

Yet we see this harassment continuing on this thread. The article I linked is just a drop in the ocean. Nitpicking over leaking bytes and language features every release is exhausting for the language author when we both know these will be fixed in another release. The fact I see activity in language and that the author is active gives me confidence in V.

pseudalopex 4y ago
> Yet we see this harassment continuing on this thread. The article I linked is just a drop in the ocean. Which comments on this thread were Xe Iaso's? > Nitpicking over leaking bytes and language features every release is exhausting for the language author when we both know these will be fixed in another release. I don't know what will be fixed in another release. Nitpicking to you was useful to decide if V was worth my time now.
- colesantiago 4y ago
  Who said it was just that person? The harassment is still continuing on this thread and has happened on other threads and posts where V is posted.
  - pseudalopex 4y ago
    You said Xe Iaso bullied and harassed the V author. I said the articles weren't bullying and harassment. You said this harassment continued. Did you mean you were wrong about Xe Iaso but other harassment started? > The harassment is still continuing on this thread I saw little or none. I understand it feels like harassment when someone believes their critics are conspiring and malicious.
    - colesantiago 4y ago
      Yes, it did, it is bullying and harassment no matter if it was past or present. I would also go to say it is pretty much toxic behavior as well, and yet it is still continuing on the V author by others in this thread. > I saw little or none. I've assumed you read the comments against V in this thread and it seems like you clearly haven't. Also, you're not the person being harassed about memory leaks after the author said this was fixed already.
      - xena 4y ago
        Hi, I'm Xe Iaso. I'm never going to write about V again. I'm only keeping my old articles up out of a desire to not break links. Even if I took it down, it's still in the internet archive's wayback machine, so there is no point in me removing my articles. If the V person unblocks me and unbans me from the places I've been banned from (at least Twitter, GitHub and Discord), I'd be happy to add a disclaimer about the post being "out of date". I want V to succeed because competition is good, but I also need to call out misleading statements for what they are. Believe what you want, but I did not write those articles in an attempt to "smear" or "defame" V or its team. I regret writing these articles as they have created negativity and hate that is slung around like candy for no real reason. I have no plans to write anything about V on my blog in the future and this experience has taught me many things about how to write about programming languages in the future.
      - pseudalopex 4y ago
        > I've assumed you read the comments against V in this thread and it seems like you clearly haven't. Try imagining someone can disagree with you. > Also, you're not the person being harassed about memory leaks after the author said this was fixed already. Disputing the author's claims is not harassment.

pseudalopex 4y ago

> Yet we see this harassment continuing on this thread. The article I linked is just a drop in the ocean. Which comments on this thread were Xe Iaso's? > Nitpicking over leaking bytes and language features every release is exhausting for the language author when we both know these will be fixed in another release. I don't know what will be fixed in another release. Nitpicking to you was useful to decide if V was worth my time now.

colesantiago 4y ago
Who said it was just that person? The harassment is still continuing on this thread and has happened on other threads and posts where V is posted.
- pseudalopex 4y ago
  You said Xe Iaso bullied and harassed the V author. I said the articles weren't bullying and harassment. You said this harassment continued. Did you mean you were wrong about Xe Iaso but other harassment started? > The harassment is still continuing on this thread I saw little or none. I understand it feels like harassment when someone believes their critics are conspiring and malicious.
  - colesantiago 4y ago
    Yes, it did, it is bullying and harassment no matter if it was past or present. I would also go to say it is pretty much toxic behavior as well, and yet it is still continuing on the V author by others in this thread. > I saw little or none. I've assumed you read the comments against V in this thread and it seems like you clearly haven't. Also, you're not the person being harassed about memory leaks after the author said this was fixed already.
    - xena 4y ago
      Hi, I'm Xe Iaso. I'm never going to write about V again. I'm only keeping my old articles up out of a desire to not break links. Even if I took it down, it's still in the internet archive's wayback machine, so there is no point in me removing my articles. If the V person unblocks me and unbans me from the places I've been banned from (at least Twitter, GitHub and Discord), I'd be happy to add a disclaimer about the post being "out of date". I want V to succeed because competition is good, but I also need to call out misleading statements for what they are. Believe what you want, but I did not write those articles in an attempt to "smear" or "defame" V or its team. I regret writing these articles as they have created negativity and hate that is slung around like candy for no real reason. I have no plans to write anything about V on my blog in the future and this experience has taught me many things about how to write about programming languages in the future.
    - pseudalopex 4y ago
      > I've assumed you read the comments against V in this thread and it seems like you clearly haven't. Try imagining someone can disagree with you. > Also, you're not the person being harassed about memory leaks after the author said this was fixed already. Disputing the author's claims is not harassment.