3 ms·

Yes, ActiveRecord is a joy to use, while Django's ORM is years behind. Right. No.

RiderOfGiraffes 16y ago
I've down-voted this, but feel I owe you an explanation. In short - I have no idea what you're saying. There are two cases - either I know about ActiveRecord and Django's ORM, and therefore I am in a position to assess what you say, or I don't. In the first case you've told me nothing except your opinion, and you've added no information. That would be worth a down-vote. In the second case, not knowing about these things I have no idea what your opinion is. I'm assuming there's an air of sarcasm, but I can't tell. Without expressing youself clearly and positively it can be hard to tell. Again, you've added no information. That would be worth a down-vote. And that's why.
- madhouse 16y ago
  I think I was quite clear that there is a sarcasm, but oh well. I responded to a vague comment which asserted that Django is "years behind", without any substantial proof, apart from "it lacks quality and maturity". Compared to that, I gave a lot more information, expressing my opinion on why that comment is far from the truth. Granted, I didn't go into details - I did mention a specific part of both frameworks, where I think one framework (Django) has a significant advantage over the other. But by all means, downrate me, but then please do that for the comment I responded to, which didn't add even as little information as I did, and only expressed his opinion without any specifics.
  - RiderOfGiraffes 16y ago
    I think you misunderstand. I didn't downvote you because your comment contained no concrete information. I downvoted you because I couldn't work out what you were saying, and there was no concrete information (in either interpretation (to me)). Sarcasm doesn't convey well in the written medium, especially when there are multiple cultures in the readership. You complain about an assertion without support, and then you appear (to me) to do the same. It's the "double whammy". If you make a bald assertion without support then - if I care - I'll ask for your reasons and evidence, but I won't downvote for that alone. You said: > I gave a lot more information, expressing my > opinion on why that comment is far from the truth. Not as far as I can tell. You may think you explained, but to me, without your obviously extensive knowledge and experience, you didn't. You say: > I did mention a specific part of both frameworks, That wasn't clear to me at all. If you had said something like: > I disagree - consider component/feature X. It seems > to me that Django is *way* ahead in that regard, and > for some applications that's far more important. ... then you'd've got an instant up-vote for me. Useful, direct and concrete information without confrontation. I hope that makes it clearer. You may disagree with that policy, but it's what I've gravitated to after some years of being here.

I've down-voted this, but feel I owe you an explanation. In short - I have no idea what you're saying. There are two cases - either I know about ActiveRecord and Django's ORM, and therefore I am in a position to assess what you say, or I don't. In the first case you've told me nothing except your opinion, and you've added no information. That would be worth a down-vote. In the second case, not knowing about these things I have no idea what your opinion is. I'm assuming there's an air of sarcasm, but I can't tell. Without expressing youself clearly and positively it can be hard to tell. Again, you've added no information. That would be worth a down-vote. And that's why.

madhouse 16y ago
I think I was quite clear that there is a sarcasm, but oh well. I responded to a vague comment which asserted that Django is "years behind", without any substantial proof, apart from "it lacks quality and maturity". Compared to that, I gave a lot more information, expressing my opinion on why that comment is far from the truth. Granted, I didn't go into details - I did mention a specific part of both frameworks, where I think one framework (Django) has a significant advantage over the other. But by all means, downrate me, but then please do that for the comment I responded to, which didn't add even as little information as I did, and only expressed his opinion without any specifics.
- RiderOfGiraffes 16y ago
  I think you misunderstand. I didn't downvote you because your comment contained no concrete information. I downvoted you because I couldn't work out what you were saying, and there was no concrete information (in either interpretation (to me)). Sarcasm doesn't convey well in the written medium, especially when there are multiple cultures in the readership. You complain about an assertion without support, and then you appear (to me) to do the same. It's the "double whammy". If you make a bald assertion without support then - if I care - I'll ask for your reasons and evidence, but I won't downvote for that alone. You said: > I gave a lot more information, expressing my > opinion on why that comment is far from the truth. Not as far as I can tell. You may think you explained, but to me, without your obviously extensive knowledge and experience, you didn't. You say: > I did mention a specific part of both frameworks, That wasn't clear to me at all. If you had said something like: > I disagree - consider component/feature X. It seems > to me that Django is *way* ahead in that regard, and > for some applications that's far more important. ... then you'd've got an instant up-vote for me. Useful, direct and concrete information without confrontation. I hope that makes it clearer. You may disagree with that policy, but it's what I've gravitated to after some years of being here.