Good luck all judges : I'm myself judging right now.

First :
-absolute madness is too slow on 83 plus calculators

Me too, and I see that many people didn't include a readme and no any rules >_<

What do you mean with rules?

Sorry for the double post, but I change of subject 

I tested 3 games, and they are all sloooooooooow ...

No, they're REALLY slow

Yes of course, but I have already seen faster Ti-Basic programs  

I saw that while judging you have to also judge this: "-Life : /5"
What is meant with Life?

Lifetime is maybe the right word for "Life":
- How long to finish the game (longer is, best it is)
- How hard is the game, the difficulty is not too hard, not too weak (it's also a part of the "gameplay")
- Does it sufficient easy to give the possibility to finish the game?

do the amount of features a program has justify its slower speed

+1
I've tested the games that they are talking about and, I was _not_ surprised by the relative slowness. Because each time I've played it, I was asking how each part was done, and I know how it's hard to simply "move a sprite, test collision, print a background and move some ennemies" quickly. In fact only move a sprite with keypress handling + handle ai require to loose the most part of the speedness.
But probably all the games will be slow in basic. Only simple games could be speed.

But in other hand, I understand that basic programmers should not add to much functionnality to keep a good gameplay.
And I understand that judges could be a little annoyed by this, even if they completely respect the incredibles programmation skills of the authors.
(Which is the case of the games we are talking about !)