many small or 1 big?

[Ken Ray]

> So what to do?  1 big with it's
> globals headaches and less safety, or many littles which sometimes seems
> silly?

Personally, if each of these apps can run independently and don't need to
run with each other, or they are (by context) different apps, you could
leave them all as separate standalones, but move all of your functions and
handlers that are to be used by all the apps to a stack by itself that you
could than have each little app "start using", thereby keeping all the code
in one place. This means that if you want to update the code, you only need
to update the "library" stack, and don't need to individually update all the
standalones. You may still need to deal with global collisions, but you get
sort of the benefits of both worlds.

Now on the other hand, if these "mini-apps" are all intending on running
together, I would make it a single app and deal with the global/safety
issues.

Just my $0.02,

Ken Ray
Sons of Thunder Software
Email: kray at sonsothunder.com
Web Site: http://www.sonsothunder.com/