Practical implementation

[addyosmani]

There's going to be a non-trivial amount of work involved in implementing TasteApp for a given framework once #1 and #2 are resolved and the spec is written.

I suggest that we begin by implementing the app using a single framework end-to-end just to help us refine the spec and evaluate how well it can be used.

Thoughts? Perhaps we could ask a member of the community to help with this or use a service like BountySource to kickstart a first implementation.

[albertosantini]

Inspired by @nicolashery comment in #1 (comment) what if we develop a tiny app demonstrating each single feature for every framework?

Maybe here I have been distinguishing between the initial feature set of the target applications (defined in #1) and the feature set of the frameworks (two-way data binding, templating (conditionals, lists, partials, etc.), nested properties, computed properties, partials, AMD support, etc.)

If we have a matrix, frameworks / features, the development would be atomic, feature per framework.
Then there would be the applications, defined in #2, demonstrating the whole thing.

With a Divide et impera approach, the effort of the startup should be more easy.

For instance, for the two-way data binding, we can develop the classic temperature converter; for the computed properties the classic list of the grocery, quantity times price, and so on.

My two cents.