Simply looking at a strip of code and visually rating can work, but only to a certain extent; especially if the script has potential. You don't want to just base a code's quality just on how one "likes it or not".
If someone were to make a very useful script in the most "concise, fastest" way possible, the concept of someone rating it a score of 1 or 2 just because he or she based it upon the creativity and the originality put into the script, is just utterly..retarded.
Rating isn't just about whether you like it or not; it's about how the code is put together, how much the intro. fully explains the script as whole, and much, MUCH more.
For those people who randomly rate a low score: Have you ever even taken a look at how the rating system works?

• 1 - (Bad,Ripped)
• 2 - (Incomplete)
• 3 - (Not useful)
• 4 - (Mediocre)
• 5 - (Average)
• 6 - (Neat)
• 7 - (Useful)
• 8 - (Very Useful)
• 9 - (Exceptional)
• 10 - (Best)So before you rate, read what the snippet poster has to say, take a look at the script, and actually TRY to TEST IT.
  If you are just not intrigued enough to even take a glance at the code, then don't bother rating. Of course, putting negative comments but with constructive criticism sounds bad, but it's better than "I rated a 1 because I didn't like it".
  Test the snippet out before you rate, or don't rate at all!