Mercury

[sindresorhus]

Mercury looks interesting.

It's like a more modular React/Om: https://github.com/Raynos/mercury#mercury-vs-react

It already has a TodoMVC app: https://github.com/Raynos/mercury/tree/master/examples/todomvc

@Raynos would you be interested in submitting it here?

[Raynos]

@sindresorhus i can submit it.

I havn't done so yet because your guideline says a framework must have a good amount of usage / popularity before submitting it.

Was going to submit something once we have real production quality proving rather then adding another toy to the todomvc pile.

[Raynos]

@sindresorhus

My style guides and such are different from the tastejs recommendations, i don't mind fixing my example to comply with your recommendations and tests and such.

However I will still want a local copy of the example that I will work in from the mercury git repository. This will lead to drift between the tastejs and mercury copy that's non trivial to port / fixup.

Do you have any best practices on how to avoid the staleness problems between two codebases ? One solution is to PR something that meets tastejs requirements into here and then have it be a little stale and periodically update it when I remember to port any local fixes back to this repo

[sindresorhus]

One solution is to PR something that meets tastejs requirements into here and then have it be a little stale and periodically update it when I remember to port any local fixes back to this repo

That's pretty much what we've been doing. We usually ping the submitter when a framework get's a new minor/major release. Not a good solution, but it works fairly well.

[arthurvr]

@Raynos Are you still interested?

[Raynos]

@arthurvr I'm have not had time to spend on Mercury recently.

I'd be happy to have Mercury in tastejs but I probably won't get around to it myself.