Remember, you cannot criticize (even though it was not it) unless you have something to show up! Next time someone provides a critique to an article, we have to make sure to let them know it is wrong to criticize unless they have written an article themselves on the same topic.

FWIW it really was just about his comment, and I made two statements: Perl is faster than Python, and that Perl is especially good for string manipulation. I do not mind that he chose Python, good for him.

▲

exe34 6 hours ago | parent [-]

For somebody who does not mind that the author chose python, you defended your opinions robustly.

	▲	johnisgood an hour ago \| parent [-]
		What opinions? Perl is faster than Python regardless of my opinion, and it is great for string manipulation, which again, is not a matter of opinion. It really is the case. None of it has anything to do with the author choosing Python. How many times do I need to repeat myself? You are the one who are being extremely defensive about it and making it seem like I give a damn about whether or not this project is written in Python. I told you I do not care. I was responding to your comment. No matter how much you insist on my reply (to you) being a criticism of the author or his project, it will not make it so. I am done talking to you, you are seeing ghosts.