This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
A program is a heavyweight process...because a program can remain in xcution for a long duration depending upon the size & complexity of the program.
But a thread is a lightweight process becaues it represents a fragment of a bigger program and can wrap its xcuition quickly or like a daemon thread start off a new thread and wait..that threads job is done.
Also in OS world, the context-switching is another factor that has to be taken into consideration.Context switching between one program and another would req few xcution cycles..The lengthier program and if there are more prgms in xcution then more prgms vie for xcution cycles(processor). but threads in contrast would not need to go thru many context switches unlike the programs.
There are other factors too like-address space,etc.
i hope this does make sense to u.
A program / thread in an OS world is a process
progm- heavyweight (time/resources needed are more) thread-lightweight (less here since it may be xcuting a part of code even though its part of the same prgm)
i originally heard it explained, years ago, as simply this: processes are "heavy weight" because starting up a new one takes a long time (on the order of milliseconds or so) - there's a lot of overhead involved. threads have less overhead, so they can be started more quickly (perhaps a fraction of a millisecond).
that might have been an incorrect explanation, however. after all, i saw it in a context of "how can we make starting a process faster in our operating system".