If you were to log in, you'd be able to get more information on your fellow community member.
I think the previous comment about the 'radical approach' encouraginginefficient code is the tip of the iceberg. In fact, I think the sampling/feedbackpart of the proposed scheme would have to be very carefully thought out in lightof the existence of Byzanine, profit-seeking people.
Lets look at some of the ways various measurement systems could be subverted:
- (measurement of component use) -- (how components can exploit this)
- %ge of CPU time component uses -- make code less efficient;
- keys/clicks directed to component-- components pointlessly graphical;
- %ge of wall time component uses -- plenty of sleep()s;
- 'operation invocation' count -- make components interfaces very complex.
I think it is fair to generalise and say that any system attempting to meter outa resource in a 'fair' manner will always fail by having its choice mechanism exploited!
One way out is to have the user decide; perhaps they rank their installed softwareevery month to say ...