Testable client side_mvc_apps_in_javascript
•Download as PPT, PDF•
3 likes•1,183 views
Overview of some technologies I've been looking at in the past few weeks
![Motivation ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (19)
Similar to Testable client side_mvc_apps_in_javascript
Similar to Testable client side_mvc_apps_in_javascript (20)
More from Timothy Oxley
Recently uploaded
Recently uploaded (20)
Testable client side_mvc_apps_in_javascript
- 1. Testable, client-side MVC apps in Javascript Demo using Spine, Jasmine, & node.JS
Editor's Notes
- Serverside technology and jobs Serverside technology and vendor lock-in Serverside technology and legacy Possible issues with browser environments becoming outdated quickly Probably a good thing though
- Your database operations should be abstracted anyway Persistence & Caching if the client has already downloaded that data why do they need to download it again Client-side prediction - quake Client should do anything it can do easily.
- in a quick bit of research, looks like less than 5%, more IE5.5 users
- Doesn't need to be complicated don't let it scare you away from making an awesome app There's always a way to fall back nicely Regressive Enhancement
- One of the best things about javascript is how fast it moves. Since beginning this 2 months ago, the hardest part has been selecting the right tools. Modernizer is a HTML5 shim and a feature detector HTML5 Boilerplate is a shim and a CSS reset also includes a bunch of css stubs. it's a little bloated and to get started you may want to go for something a little more lightweight
- Variables Mixins Cross-browser Templates
- CSS not included
- No Tests, Bugs around every corner No guarantee that the app actually works Rigorous manual testing means testing doens't happen Unprofessional Documentation The original developer(s) only person who can fix bugs without inducing homicidal rage Documentation gets out of sync if it's too heavy only when totally necessary "Refactoring? Just write it well the first time" Code gets worse with time Urge to rewrite each piece of software every 6 months Knee-jerk Methodology Always in crisis mode Impossible to keep deadlines Overworked staff Minimal technology options Sticking with what you know Don't fix it if it ain't broke When all you have is a hammer everything looks like a nail
- There are others but these ones are most general. Allows you to identify 'code smells' in any language Surprising how many people don't read this kind of material These books make it easier to communicate ideas and me not sound like a madman with strange ideas designed to ruin projects