the "MVC" nomenclature came from traditional desktop apps, no? RoR just followed suit. So, I always "hated" RoR, because it was full of hidden conventions and

the "MVC" nomenclature came from traditional desktop apps, no? RoR just followed suit. So, I always "hated" RoR, because it was full of hidden conventions and regular black magic. At least PHP was globally simple and primitive, even if locally ugly and complex. I still remember Misko's early(est?) Angular announcement video, it was just part of GTAC [google test automation conference], and the whole thing was about testability. https://www.youtube.com/watch?v=gQclnI_8Vmg https://www.youtube.com/watch?v=gQclnI_8Vmg It was seen as natural separation of concerns, it was seen as - finally - breaking free of the big bulky backend (of GWT and the shackles of semi-autogenerated frontend code) the frontend runs on the browser anyway, it needs to manage its own state anyway, etc, etc. Of course this only emphasizes your point, that a good ~95% of the sites are not like this, they shouldn't even try to manage state on the frontend. > Once you get into the range of applications that really need an SPA they let you down. Yep. I wholeheartedly agree.