You are welcome.

My mental filter is aimed at:
- a fwk being strongly opinionated towards MVVM or MV_P (upd: Model View Presenter, not the MVP elongated: in short Adherence to onion layer principle) Mithril controler instantiating a VM and calling itself MVC ***and*** MVVM is good enough for my taste to fall into that category
- viewing client GUI state (not DB-persisted data) as a DATA part of the VM/P layer, not trying to build fragile code/event patterns, dependency injection scattered all over theplace
- code lean enough VM is only an object augmented with a UI-specific child object or P is only an a function based on a VM-like prototype -
dunno if a dynamic mixin would be grouped with MVVM or MVP by POOP classificators ;-)
- components seen as a viable target

React and Aurelia the other projects important enough for me to regularly look in - at the moment not for project use, but to stretch borders of JS knowledge and compare my architectural map of how the ideal fwk should be build with things currently hot. When Angular2 hits the masses probably another one to add to the list, even if only to be able to prick a few bullshit bingo balloons.

On React on Youtube a video about retinking best practices [Pete Hunt], which gave words to quesy feeling I get reading the heavy templated and logic-infused HTML style following Angular1 like approaches create - while the Mithril "m" style also feels forced/unnatural, putting heavy logic into HTML feels worse. If I find time to write an answer to Hank more on that.

I believe I already mentioned NWjs aiming at similar targets as Electron a while back - it is just the one I encounterd earlier.

Recently added to reading list from the perf POV angle: Resig from jQuery fame and Zakas - the latter has some advice for building scalable solutions, which includes wrapping components in a function to provide "sandboxing" - something between "enforcing" a poor mans interface and a facade, which sounded still lean enough to me and would help if one needs to switch fwks by enforcing isolation. Reccomended and DRY-elegant even under Python standards, easy to google.

Still on my reading list: Meteor, the SQL attempts in Atmosphere, now Apollo with GraphXL. Meteor is funny: about the only ones realizing client side DB / cursor / cache with identical API is a huge benefit: When I read their 7 principles, first thought was "Finally!". Then I read in detail, what they target with their DB-reactivity and realized that Mongo might be more than just the demo first implementation, but that the whole concept might depend on it.
Now switching to GraphXL reminds me of the old Get Smart "missed by that much" line - it was a recurring theme... ;-)

If you (or somebody else with similar warped taste) have encountered some other projects, articles, blogs or videos falling into that architecture/best practices/proven-performant area (not neccessarily in JS - might also be in Python, Java or C#) just name them. My voracious reading tendency has not been classified as illness.

regards

thomas

>Thank you - I took a close look at Vue. I like it. It's not to hard to understand and it appears to be very fast - but it's small. I doubt it's the fastest out there but it's fast enough for a CRUD app.
>
>Again thanks for the lead!
>
>Johnf