1 day ago, JoshRoss wrote
Once I accepted that a single do-it-all framework didn't exist and that was ok, did I really start to appreciate how well all these frameworks are designed, maintained, and function.
100% agree... in fact, i ripped out all the breeze stuff and am doing my own datacontext 'service' just using basic jquery xhr requests and to my amazement everything worked the 1st time by just following the demonstrated pattern with the included logger service.
the way things are wired up by default (as long as you follow naming conventions), you get an automatic 'merging' of the current viewmodel onto the view for ko binding, but you don't even HAVE to use this. if you choose to, you can just handle viewAttached() in the viewmodel (which acts a lot like the docready() in jquery, although this admittedly gets away from the declarative binding that ko brings and puts you back in the 'select and modify' pattern... i'm okay with that for now).
the durandal framework exposes a few 'page-like' events that are very, very convenient. all you have to do is define them as functions, export/expose them through the viewmodel and they get called when the page (viewmodel) activates, deactivates, viewAttached, CANdeactivate, etc... SUPERB stuff.
you can do so much from this starting point, if you just know a couple of the quirks/hacks. i'm still trying to wrap my head around the functional/promise/async aspects of the js language. things that look like hacks to me are embraced language features!