On 2010-01-24, at 06:39 , Jim Puls wrote: > > On Jan 24, 2010, at 12:36 AM, Caio Chassot wrote: > >>> But we also have to test with *100* windows open. Because that's just what >>> happens whenever you allow multiple of something. (There are people who >>> have 20,000 tabs in my app. Whenever you allow multiples of something, >>> there will be people who go far, far beyond whatever you expected.) >> >> And because I hope we'll be VERY PITA about persisting state, this is >> trouble squared. Crazy users will just keep growing their workspace over >> sessions, and we'll have to make damn sure we can serialize and reload >> everything just as it was. > > How is serializing and reloading 100 windows any more difficult than > serializing and reloading just two?
In theory, none. In practice, things go wrong. When we have more things, more things go wrong. With 100 windows, there's more chance one of them is in a state which leads to a serialization bug. Or to a reloading bug. Which we never catch because it's one in 100 windows, and we don't notice. Or it's a speed thing. If you test with 100, and it performs fine, it may start acting wonky at 200, taking seconds and seconds to load. Maybe at 1000 if you were clever. Maybe only at 32768, for very indirect reasons. You know. Programming is not deterministic. Shit happens. A lot. _______________________________________________ [email protected] mailing list List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
