1. The Blast Mojo Framework Loyal Chow | Technical Experience Director
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
Editor's Notes
11/15/09 06:53
Each developer has their own history, opinions and preferences in utilizing a varied number of JavaScript libraries such as jQuery, Prototype, MooTools, Dojo and YUI. To any developer and their team, the cost of utilizing these libraries were seen as a means to save developer hours, allow development to react to creative needs and stabilize estimation due to each libraries centralized, tested code base, good API and strong communities. What we noticed within our team environments were other incurred costs that ended up eliminating the savings of the use of these libraries. We found that the foundation, the blue print that would drive the structure of the interface would be specifically tied to one or two individuals thinking. This thinking required a number of hours to ramp-up any new developers to the project(s), the code eventually became so customized, under documented and complex that we were left with little or no reuse and no take away from the project. We were leaving the client with a code base that would require another rewrite when the next refresh was to take place. In short, we found ourselves building the same systems from the bottom up each and every time using a number of 3 rd party libraries. What we needed was a good stable starting point. 11/15/09 06:53