3 ms·
That's how you do a client-side framework or any framework for that matter, forward thinking with backwards compatibility and no custom nonsense tying it to a s
by dkarapetyan 12y ago
That's how you do a client-side framework or any framework for that matter, forward thinking with backwards compatibility and no custom nonsense tying it to a specific language (AtScript).
- watty 12y agoCompletely agree on backwards compatibility but AtScript isn't required for Angular 2.0.
- TheSisb2 12y agoIs this backwards compatible? I thought Evergreen browsers meant IE10+
- dkarapetyan 12y agoI meant in terms of the design of the framework and the emphasis from day 1 on making everything modular and interoperable with the rest of the JavaScript ecosystem, e.g. jQuery, Knockout.js, etc.