I agree that insightful reviews deserve more points than answers that are merely linting. However, I believe that no answer should be downvoted unless it contains advice that is actually harmful.

Code Review's policy is to allow critique on any and all aspects of the code. As per in Let's work together to offer ultimately better content, faster and Short answers, we don't require any single answer to be a comprehensive review, or even an attempt to be comprehensive.

I'd much rather enforce a policy that all critiques be given as answers, so that they can be voted and commented on. Disallowing trivial answers would merely encourage people to post those remarks as comments, which would make a mess.

Instead of downvoting trivial answers, let's focus on upvoting insightful reviews.

I agree that insightful reviews deserve more points than answers that are merely linting. However, I believe that no answer should be downvoted unless it contains advice that is actually harmful.

Code Review's policy is to allow critique on any and all aspects of the code. As per in Let's work together to offer ultimately better content, faster and Short answers, we don't require any single answer to be a comprehensive review, or even an attempt to be comprehensive.

I'd much rather enforce a policy that all critiques be given as answers, so that they can be voted and commented on. Discouraging trivial answers would merely encourage people to post those remarks as comments, which would make a mess.

Instead of downvoting trivial answers, let's focus on upvoting insightful reviews. If you think that an answer is merely "meh", then I suggest that you not vote on it at all.