The usage of simple javascript objects meant it was easier to integrate than other frameworks, but required a little more heavy lifting to make the bindings more transparent. The fine-grained dependency tracking allowed for extremely fast updates, but was implemented with a centralized data structure that did not work well on our low powered devices. We found the observable system to be robust and generic, but at the cost of management overhead and complexity. The team preferred the syntax and features of Knockout, so we used it as a base and dove deep into the internals, reviewing how it handled view management, memory management, update computations, and DOM rendering. Initially, our thought was to rework an existing framework to fit our needs. Designing and Experimenting with an Existing Framework It also had to run as fast as possible with a JS engine in interpreter mode, and be flexible with the number of concurrent DOM trees it could interact with.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |