Why Angular?
(or really, why ANY client-side VC* framework?)
Eliminate boiler-plate code
-
Event binding
- Built-in code-organization constructs
- Discreet separation of concerns means testability
- Public sector is moving to VC* because:
- SAVES TIME AND MONEY
- Easier to on-board new developers
- Into Angular apps vs Ad-hoc javascript applications
- Less ramp-up time
- Concepts are consistent across projects
- Code is organized similarly across projects
- Helps prevent spaghetti code
- Benefits strongly realized when projects grow in size
BRowser support
-
Modern browsers (recent versions of Firefox/Chrome/Safari)
-
IE8 supported in Angular 1.2
-
IE9+ supported in Angular 1.3
ANOTHER OPTION (EMBER)
Ember is going to support IE8:
"Despite the imminent End of Life status of Windows XP, we will continue supporting Internet Explorer 8. We know many Ember.js users still need to target enterprise and education customers, who will be on IE8 for some time."
Same basic concepts as Angular, but little more opinionated in the design.
Browser version support
Need to establish realistic baselines for browser support
IE8?
IE7??
IE6??????
-
Any information via analytics for browsers our customers use?
-
Need to make sure we don't have too many IE7 false positives
-
IE8 in IE7 compatibility mode *probably* comes through as IE7 in most analytics tools
