Many Cards Versus One Card and a List Field

[Mark Smith]

Russell, how much data and how many cards do you envisage using?   
There are many ways of storing data in Revolution, and good  
performance is not necessaily hard to achieve.

Can you describe your project a bit?

Best,

Mark
On 14 Jan 2008, at 18:49, Russell Martin wrote:

> I realize I'm kinda late to the party on this topic, but I just  
> want to
> express my dismay at finding out that using stacks as databases is
> prohibitively slow. That just seems bassackwards.
>
> A big part of why I started looking into HyperCard, SuperCard, and  
> then
> Revolution was because I finally got the genius of the stack of cards
> paradigm. Now, I'm being told that the time and effort I've spent
> learning how to create template stacks within my projects, clone them,
> write them out to disk, and keep my code for their buttons, etc.  
> inside
> of another stack in my project is all for naught because I should have
> been learning how to store information in delimited list fields?
>
> Is anyone else bothered by this? Instead of programming around the
> stack, shouldn't we be clamoring for Revolution to fix this  
> performance
> problem? I mean, if I can't realistically store large amounts of data
> in stacks (and get acceptable speed), then what is the point of  
> using a
> stack based development tool? If I have to store my data as a big
> delimited chunk of text and develop methods of iterating through it  
> and
> then populating UI elements from it, then I might as well be using any
> other dev tool.
>
>