> TL;DR Modern JS app-building frameworks & libs share one quality - they are component-based. Why not use this (high) granularity to bundle components into small, user journey-focused micro-apps instead of building humongous, complex SPAs. Such model, if applied properly, may bring certain qualities usually associated to microservices into...
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: >...
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 [http://angularjs.blogspot.com/2014/10/angularjs-130-superluminal-nudge.html] is a major update that was supposed to prove that Angular....
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...
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)...
