Hi Tim,

What tinyBenchmarks performance do you get?

I use Cuis all the time on an Atom netbook (Cog, 29Msends/sec,  
180Mbytecodes/sec). Cuis is nice to use here.

 From time to time, I run it on my XO (300MHz Geode, Cog,  
6.2Msends/sec, 39Mbytecodes/sec). Cuis is pefectly usable here.  
Sometimes I also run it on a PIII with a CPUKiller app, that brings  
performance down to XO levels.

Using slower machines is really useful. It really helped me find code  
that really deserved some optimization. The result is that, even if it  
looks cool, Cuis is usable on slow hardware?

Have you tried Cuis on the Pi? Could you please do it and comment on  
the experience?

BTW, if needed, you can evaluate 'Preferences slowMachine' to trade  
looks for responsiveness.

Cheers,
Juan Vuletich

Quoting tim Rowledge <tim at rowledge.org>:

...
>
> FIrst suspect has to be stuff added to the step code that hasn't  
> been carefully thought about for speed. Too many people just assume  
> a faster machine will come along Real Soon Now and solve the problem  
> for them. Ain't gonna happen any more. Single core performance has  
> hardly changed for several years, multi-core performance is blocked  
> by memory performance and cost per transistor is flat.
>
> I propose that everybody buys as Raspberry Pi to run their code on  
> and at least tries to improve it for performance once in a while.  
> For $35 it's a really cheap software development tool.
>
> tim
> --