the expense of features
Posted in Dojo, JavaScript, Tech on February 10th, 2007 2 Comments »
With Dojo, we’ve recently been discussing splitting up the toolkit into better, easier to digest, less “expensive” code. To which I asked myself, what does expensive mean, for the creators and users of Dojo?
download size
number of requests
CPU utilization
memory usage
# of browser/scenario forks
complexity/time to get started
error-proneness
maintainability
testability
marketability
interoperability
competitiveness
distribution