4 ms·

Ever wanted to see a bad argument? Read the post by Dylan16807!

• Dylan16807 14y ago
  As long as you're linking a specific post, go for it. I've made mistakes. But I'm going to hope it's not just a post you disagree with. Just like I hope you don't call code bad because it uses OTB or omits semicolons. It should be failing to solve the problem it sets out to solve, and in an interesting manner. (Note: I have not looked at the code tweeted about.) Edit: Wait how did THIS post get downvoted? I can understand the earlier posts but I can't even imagine what's objectionable about this one.
  • cygx 14y ago
    Don't know, but possibly because you're derailing the discussion. The outrage is not about constructive (or even unconstructive) criticism of the code itself (which appears to be fine): At least one of the guys ridiculed the author and questioned her competence for the sole reason of implementing a subset of the features of GNU find+sed on top of Node.js.
    • Dylan16807 14y ago
      Well then maybe those people should have been mentioned in the article. When I see top-level comments I don't realize I have to read hundreds of comments they are replying to without using the reply button. I was only talking about the examples given up front, which insulted the code, not the author. Thank you for the useful info.