javascript architecture: the front and back of it
UI Architecture: all the stuff that it takes to process, package, deliver, and communicate with the client (templating url routing, data validatiion, formatting, ajax). “Between the front and back end”: stuff between presentational javascript and the backend logic. The middle end gives a web 2.0 app performance.
We need to talk about this because of issues with performance and optimization, the MVC model spaghetti code failure (outputting html if a condition exists: the mixture of model code inside view template, too tight coupling between presentation layer and model layer), “don’t repeat yourself” (DRY: repeating code over and over again, i.e., duplicating validation in the client and the server, “any time there is more than one copy of something, one copy is always wrong”), and role separation (wearing multiple skillset hats and mixing contexts–markup/css switch to javascript switch to backend app–without being able to focus on one context at a time).
This isn’t another framework, it’s an optimized/reworked “alternate pattern” of MVC in an attempt to solve some of the weaknesses/problems of MVC. Can we decouple the view from the existing architecture stack?
CVC + JavaScript puts the power of UI architecture in the hands of front-end engineers.
- Presenter(s)
- Kyle Simpson
- Date
- 14 March 2010
- Tag(s)
- #frontandbackofit
- #jsarch
- Sites
- Getify
- Demo of HandlebarJS
- Speaker Feedback
- BikechainJS
- HandlebarJS