Breaking backwards compatiblity

H. S. Teoh hsteoh at quickfur.ath.cx
Sun Mar 11 20:10:54 PDT 2012


On Sun, Mar 11, 2012 at 11:38:12PM +0100, deadalnix wrote:
> Le 11/03/2012 21:06, Walter Bright a écrit :
> >On 3/11/2012 4:20 AM, Matej Nanut wrote:
> >>I've been using an EeePC for everything for the past 2.5 years and
> >>until now, I could cope.
> >
> >You're right that there's a downside to providing your developers the
> >hottest machines available - their code tends to be a dog on the
> >machines your customer has.
> >
> 
> I think a better solution is including expected performances in the
> user stories and add them in the testing suite. Dev can enjoy a
> powerful machine without risking to get a resource monster as a final
> executable.

Even better, have some way of running your program with artificially
reduced speed & resources, so that you can (sortof) see how your program
degrades with lower-powered systems.

Perhaps run the program inside a VM or emulator?


T

-- 
It's bad luck to be superstitious. -- YHL


More information about the Digitalmars-d mailing list