Integration analogy
from 
WinCustomize Forums
WinCustomize Forums
At the risk of re-opening a can of worms, it occurred to me that maybe what is needed to discuss the question of bundled vs integrated is an analogy.
Saying that XP skins are 'native' because they are integrated can lead to a fairly technical discussion, at least by the standards of novices.
So how about this as an analogy? When I installed windows2000 at home, one of the components that automatically got installed is notepad. So, notepad "must" be a native and integrated part of the OS. As a comparison, look at object edit. Since this has to be installed, it is "obviously" far more power hungry, and probably not worth the overhead.
Now these are both simple, quick to load, text editors. So this line of argument sounds quite silly, and since they are single items it should be easy to say "look, here are the resource usage figures, and here are the extra things object edit provides".
Perhaps this isn't a good analogy, but it is the one that came to mind. People often seem to prefer simple, easy to follow, illustrations of what is going on, and these can be quite convincing, not to mention misleading
Well, I thought I would suggest it, since pointing out what is going on at a low (dll) level isn’t always that easy to understand.
Saying that XP skins are 'native' because they are integrated can lead to a fairly technical discussion, at least by the standards of novices.
So how about this as an analogy? When I installed windows2000 at home, one of the components that automatically got installed is notepad. So, notepad "must" be a native and integrated part of the OS. As a comparison, look at object edit. Since this has to be installed, it is "obviously" far more power hungry, and probably not worth the overhead.
Now these are both simple, quick to load, text editors. So this line of argument sounds quite silly, and since they are single items it should be easy to say "look, here are the resource usage figures, and here are the extra things object edit provides".
Perhaps this isn't a good analogy, but it is the one that came to mind. People often seem to prefer simple, easy to follow, illustrations of what is going on, and these can be quite convincing, not to mention misleading
Well, I thought I would suggest it, since pointing out what is going on at a low (dll) level isn’t always that easy to understand.
