| "We all know why one might prefer something over Electron." Actually, that's not true. There are most likely some folks reading who don't know much about Electron. Also, just because there are a number of well known reasons why someone might dislike Electron doesn't mean that they are this person's reasons for disliking it. Perhaps he has reasons for disliking it of which you are unaware. If you don't want to bother asking him that's fine, but that doesn't make the question not worth asking to everyone else. "'Ugh, the color blue! Me no likey!' Does it really matter why they don't like blue, or whether I agree with them?" Not liking the color blue isn't even close to the same thing. Peoples likes and dislikes about colors are very subjective, and people often don't have any definable reason for why they like or dislike a color. That is very rarely true about development tools, frameworks and libraries. If a developer does not like them, they usually have a particular list of reasons why. You may disagree with their reasons, or the way they present them, but you still might learn something of value from hearing their list. "It's just a worthless comment." It's only a worthless comment to you because you made assumptions about why the comment was made. I understand why you might be put off by the way the original comment was worded, and yes I would have preferred that they elaborate more about the reasons for their dislike of the choice of Electron up front. However, I think it is a mistake to assume that you could not have learned anything of value from engaging with the person who left that comment (instead of assuming you already knew what the reasons behind it were.) |