Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implementation Descriptions #7

Open
dprotti opened this issue Jun 13, 2014 · 1 comment
Open

Implementation Descriptions #7

dprotti opened this issue Jun 13, 2014 · 1 comment

Comments

@dprotti
Copy link
Contributor

dprotti commented Jun 13, 2014

Continuation of #894:

TodoMVC added value AFAIK is: it fixes the characteristics of a product to be built, then asks producers to build a compliant product (not > necessarily identical to others), easing comparisons between producers.
I think TodoMVC shouldn't put effort into touching/handling/hosting producer's code.

About project listing, some ideas for the question What do I want when I look for a framework?:

Overview

Samples

  • Snippets
  • Whole apps

Goal: reason of existence

I like to see: design patterns used, relationship to other solutions/technologies

I don't like: buzzwords ("to build fast, scalable...", "easy to maintain..." and similar)

What is it very good for (outstanding) and why

Key Things: list of ~5 framework-specific classes/objects/concepts I must necessarily know about to properly use the framework
Current state

Starting | in Beta | Used in Prod by online sites {X, Y, ...} | etc.
Starting year, # of past and current maintainers
Dependencies

Community

Mailing lists, groups, etc.

Docs

Articles & Guides

Some things (Community, Current state) applies only to frameworks and no to usage samples of framework combinations.

Sounds good? For sure needs to evolve but do you think it's a starting point?

A sample implementation info following these guidelines is at https://github.com/dprotti/TasteLang#implementations.

That's about What do I want when I look for a framework?

About the question What do I want when I want to compare frameworks?:

First, I like to see only what is relevant to my comparison. Examples:

  • Only frameworks that have dependency X
  • Only frameworks that use design pattern W
  • Only frameworks in X state of development, or more/less than Y years old
  • etc

So I think it's valuable to have some kind of filtering / grouping mechanism for frameworks listing. I'm not sure how this can be accomplished using Github wiki features, but whatever the final solution is it would helpful if we uniform the fields describing the project info.

@sindresorhus
Copy link
Member

@tastejs/todomvc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants