3 ms·

Ok glad you voiced your opinion that you disagree. I hope you feel better now, since it's clear what I have to say is so true that you're tormented to post a re

Ok glad you voiced your opinion that you disagree. I hope you feel better now, since it's clear what I have to say is so true that you're tormented to post a response. Next time that would be better done with a downvote because you have zero to add. Reading comprehension is key. I was defending against those creating conflict. There's nothing more political than Python3. And overthrow all BDFLs. That was the whole point, that went right over your head. You are not an engineer. Go back to Reddit. The irony of lazy people calling other people lazy is pretty hilarious. Since you harass the PyPy team and 90% of the Python community to port to 3 while you remain a non-contributing zero? There's only one thing to say to you: Get to porting.

dang 11y ago
This comment breaks the HN guidelines, and unfortunately you've been doing so quite a bit in other comments too. We ban accounts that do this, so please stop doing it. Instead, please (re)-read the following and post civilly and substantively or not at all: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newswelcome.html https://news.ycombinator.com/newswelcome.html
- BuckRogers 11y ago
  I read those links and as far as I see, I was confronting other folks who were breaking this rule- 'Please avoid introducing classic flamewar topics unless you have something genuinely new to say about them. ' While adding a lot of new substance to a topic that breaks the mold of "port PyPy to Python3" and how to achieve those goals. Perhaps my tone was a little strong and regrettable. I did break this one by accident but mostly out of frustration to a substanceless post. I regret the error. 'Please don't bait other users by inviting them to downvote you or announce that you expect to get downvoted. '
  - dang 11y ago
    Glad to see you calling attention to HN's anti-flamewar rule. You're right that it is an important one, and people unfortunately break it all the time. Still, a "confronting" response just makes things worse, and one violation of the HN guidelines doesn't justify another. It isn't easy to remain civil and substantive in response to comments that break the rules, especially when one is annoyed. I don't get it right all the time myself.

dang 11y ago

This comment breaks the HN guidelines, and unfortunately you've been doing so quite a bit in other comments too. We ban accounts that do this, so please stop doing it. Instead, please (re)-read the following and post civilly and substantively or not at all: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newswelcome.html https://news.ycombinator.com/newswelcome.html

BuckRogers 11y ago
I read those links and as far as I see, I was confronting other folks who were breaking this rule- 'Please avoid introducing classic flamewar topics unless you have something genuinely new to say about them. ' While adding a lot of new substance to a topic that breaks the mold of "port PyPy to Python3" and how to achieve those goals. Perhaps my tone was a little strong and regrettable. I did break this one by accident but mostly out of frustration to a substanceless post. I regret the error. 'Please don't bait other users by inviting them to downvote you or announce that you expect to get downvoted. '
- dang 11y ago
  Glad to see you calling attention to HN's anti-flamewar rule. You're right that it is an important one, and people unfortunately break it all the time. Still, a "confronting" response just makes things worse, and one violation of the HN guidelines doesn't justify another. It isn't easy to remain civil and substantive in response to comments that break the rules, especially when one is annoyed. I don't get it right all the time myself.