In a way, it is the users fault. As soon as you venture into the wild forest that is community made software, you're running the risk of getting the blame when things break and often there are actual bugs that cause the problems.

Wanting some cool widget hot from the developers fingertips is ok as long as you, as the end user, is prepared to be a guinea pig. Sadly this is also true for some of the Nokia code...

Regarding your suggestion, I think it might be a little too costly to have separate processes, as in one per widget. Threading, on the other hand, would be much more interesting. This way, the main widget process would be able to kill threads at its leasure if need be without the added cost of having a whole new process.

Separating the different widgets from eachother is a good idea.