HN > Techcrunch story > Google Search for paper mentioned > Ch1 of paper, which had this nugget:
"I noticed that, often, the mere presence of a feature or capability incurs some cost, even when not being used. For example, as the number of services and options multiply, extra code is required to select from among them, and to check for possible interference between them. This code does no useful work processing the application's data, yet it adds overhead to each and every call."
"I noticed that, often, the mere presence of a feature or capability incurs some cost, even when not being used. For example, as the number of services and options multiply, extra code is required to select from among them, and to check for possible interference between them. This code does no useful work processing the application's data, yet it adds overhead to each and every call."
I like this idea of the presence of code causing things to change around it - seems like something that can be quantified usefully by GUTS.
No comments:
Post a Comment