Few days ago I had a short discussion about an idea for a webapp (publicly available, commercial, you know - all the usual stuff). As I am doing a lot of stuff in web nowadays & I've made few SPAs with different libs recently, I was asked:
"Which SPA library / framework would you use today?"
My interlocutor was utterly surprised with my answer:
The waiting is over, it's already here. Maybe it doesn't resolve all the concerns (yes, concerns, I wouldn't even call them issues), but 1.3 is a major update that was supposed to prove that Angular.js is evolving & community's voice is being taken under consideration.
If you want full list of changes, you have to check here. Below you can
I've spend some time on prototyping a modular SPA hub that meets the following core requirements:
- from users perspective - it all looks like one app (seamless navigation, same looks, shared layout, etc.)
- it consists of independently developed (by different people) modules, BUT these modules may use other modules' presentation elements (on some established level)
- modules are supposed to be automatically testable (incl. presentation
Modern JS app frameworks / libraries that follow the SPA paradigm (static content + JS app + JSON data via XHR) have changed the way you can track your users’ activities - monitoring HTTP requests to the server is not enough as client-side routing (like the one in Backbone.js or Angular.js) doesn’t have to make any actual request at all!