Quoted post unavailable.
Quoted post unavailable.
No post body was provided.
How to Build an Evil Compiler
31–38 of 38 posts
Re: How to Build an Evil Compiler
#32Earlier quoted context omitted.
Quoted post unavailable.
Quoted post unavailable.
Yes, why would you? It has zero information content. What should users do there? Comment on old threads instead of the current one? That's ridiculous.
You may have noticed people linking older discussions and may try to emulate it, but they do it when the older discussion has multiple and relevant comments.
And you seem to do it all the time. Please stop.
Re: How to Build an Evil Compiler
#33Earlier quoted context omitted.
Quoted post unavailable.
Yes, why would you? It has zero information content. What should users do there? Comment on old threads instead of the current one? That's ridiculous. You may have noticed people linking older discussions and may try to emulate it, but they do it when the older discussion has multiple and relevant comments. And you seem to do it all the time. Please stop.
I'm not sure why _you_ think it's appropriate to repost a very fresh article (e.g. still open for discussion) that had no traction. Search recent. Post if not there. Do not post if there.
I link to recent reposts "all the time" (actually less than 5% of my average one comment per workday) because people seem to misunderstand this procedure. The rules are clear about limiting reposts and carefully curating submissions.
I link all the time because often, the original poster (and, in this case, the author of the original post) deserves some of the karma that unlocks their ability to better interact with the HN community, because neither @hackthesystem nor @awelm_ nor @awelm (whoever the real awelm is) has enough karma to even change the top bar color...
I do it all the time to highlight the blatant unsavory behavior of serial reposters---in one recent case, linking both posts (from the same user, posted two days apart) of a Wikipedia URL to one another. This is not quality content, and I hoped some other users would notice and flag.
Now, I am not continuing this conversation because I have real work to do, and nothing more we say to each other will prove to be "thoughtful and substantive".
Re: How to Build an Evil Compiler
#34Earlier quoted context omitted.
Yes, why would you? It has zero information content. What should users do there? Comment on old threads instead of the current one? That's ridiculous. You may have noticed people linking older discussions and may try to emulate it, but they do it when the older discussion has multiple and relevant comments. And you seem to do it all the time. Please stop.
I'm not sure why _you_ think it's appropriate to repost a very fresh article (e.g. still open for discussion) that had no traction. Search recent. Post if not there. Do not post if there. I link to recent reposts "all the time" (actually less than 5% of my average one comment per workday) because people seem to misunderstand this procedure. The rules are clear about limiting reposts and carefully curating submissions…
You're obviously abusing your flagging privileges (flagging reposts which are explicitly allowed on HN — read the rules!), and I hope people will join me in flagging your link spam.
You're right, people like you will never reform, so there's nothing more to discuss.
Re: How to Build an Evil Compiler
#35Earlier quoted context omitted.
Yes, why would you? It has zero information content. What should users do there? Comment on old threads instead of the current one? That's ridiculous. You may have noticed people linking older discussions and may try to emulate it, but they do it when the older discussion has multiple and relevant comments. And you seem to do it all the time. Please stop.
I'm not sure why _you_ think it's appropriate to repost a very fresh article (e.g. still open for discussion) that had no traction. Search recent. Post if not there. Do not post if there. I link to recent reposts "all the time" (actually less than 5% of my average one comment per workday) because people seem to misunderstand this procedure. The rules are clear about limiting reposts and carefully curating submissions…
Wow, you doubled down. I agree with Tomte. Linking to a 3-day-old submission with 0 comments is worse than useless, it's just spam, and wastes peoples' time if they click on them, having assumed nobody would post a link to an empty page. Yes, it looks like you do that all the time, more like 50% than 5%. "blatant unsavory behavior"?! That describes your comment and your linking to empty pages, but nothing else I can see here. Please stop bothering with your crusade, it detracts from rather than adds to HN.
Re: How to Build an Evil Compiler
#36Earlier quoted context omitted.
I'm not sure why _you_ think it's appropriate to repost a very fresh article (e.g. still open for discussion) that had no traction. Search recent. Post if not there. Do not post if there. I link to recent reposts "all the time" (actually less than 5% of my average one comment per workday) because people seem to misunderstand this procedure. The rules are clear about limiting reposts and carefully curating submissions…
You're obviously abusing your flagging privileges (flagging reposts which are explicitly allowed on HN — read the rules!), and I hope people will join me in flagging your link spam. You're right, people like you will never reform, so there's nothing more to discuss.
Please don't do this tit-for-tat spat thing on HN. It's way out of line, no matter how right you are or feel you are.
Re: How to Build an Evil Compiler
#37Earlier quoted context omitted.
Yes, why would you? It has zero information content. What should users do there? Comment on old threads instead of the current one? That's ridiculous. You may have noticed people linking older discussions and may try to emulate it, but they do it when the older discussion has multiple and relevant comments. And you seem to do it all the time. Please stop.
I'm not sure why _you_ think it's appropriate to repost a very fresh article (e.g. still open for discussion) that had no traction. Search recent. Post if not there. Do not post if there. I link to recent reposts "all the time" (actually less than 5% of my average one comment per workday) because people seem to misunderstand this procedure. The rules are clear about limiting reposts and carefully curating submissions…
Reposts like that are ok on HN because we want to give good articles multiple chances at getting attention. Threads stay open for discussion for two weeks but are lucky if the window for getting on the front page is even two hours.
It's true that a better system could share the karma for a successful post between all the submitters, and that's actually on our list to implement. In the meantime, though, the current practice is a good thing because it mitigates some of the randomness of what gets traction off /newest and (sometimes) prevents good articles from falling through the cracks.
https://hn.algolia.com/?sort=byDate&dateRange=all&type=comme...
https://hn.algolia.com/?sort=byDate&dateRange=all&type=comme...
Re: How to Build an Evil Compiler
#38Link appears to be broken. There is a mirror located here: https://gcc.gnu.org/