4 ms·

This is a very useful resource, and it really is great to see it being done in such a professional manner, but I can't help but wish for the end of these Todo<b

This is a very useful resource, and it really is great to see it being done in such a professional manner, but I can't help but wish for the end of these Todo<blah> examples. A todo app simply isn't complex enough to give users any sort of insight into which framework to choose. There are so many other areas that are important yet completely uncovered in the code - things like authentication, ACL, mobile support, and plenty more examples that I just can't think of off the top of my head right now. The idea behind this is fantastic, the execution is incredible, but the project choice is too limited in my eyes.

deleted 14y ago
[deleted]
joelhooks 14y ago
The difficulty is that anything more complex is TOO complex as an example. This is meant to demonstrate the MVC of a thing. With this example, I can quickly examine the structure and feel of a given tool, an hold the entire example in my head. When you start stacking all of the other bits on too, this starts to become more difficult. What TodoMVC allows is a quick survey to narrow down contenders. At that point I can examine the other crucial aspects and understand if they work for my project.
- AndrewNCarr 14y ago
  >The difficulty is that anything more complex is TOO complex as an example. This sums it up. "Todo" examples are intended as a web/js-framework equivalent to the traditional "Hello World" example used to introduce a programming language. "Todo" defines a basic unit of usefulness that can be easily implemented to give the target audience an idea of what a given framework "looks like". It isn't perfect, but it is a starting point for framework comparison.
stevewilhelm 14y ago
Couldn't agree more. Todo doesn't come close to exposing the actual strengths or limitations of a given framework.
elchief 14y ago
"Set the bar so low, no one cares if you succeed" - Homer Simpson Something like Google contacts, or Gmail if you wanna push your luck, would be more appropriate.

deleted 14y ago

[deleted]

joelhooks 14y ago

The difficulty is that anything more complex is TOO complex as an example. This is meant to demonstrate the MVC of a thing. With this example, I can quickly examine the structure and feel of a given tool, an hold the entire example in my head. When you start stacking all of the other bits on too, this starts to become more difficult. What TodoMVC allows is a quick survey to narrow down contenders. At that point I can examine the other crucial aspects and understand if they work for my project.

AndrewNCarr 14y ago
>The difficulty is that anything more complex is TOO complex as an example. This sums it up. "Todo" examples are intended as a web/js-framework equivalent to the traditional "Hello World" example used to introduce a programming language. "Todo" defines a basic unit of usefulness that can be easily implemented to give the target audience an idea of what a given framework "looks like". It isn't perfect, but it is a starting point for framework comparison.

stevewilhelm 14y ago

Couldn't agree more. Todo doesn't come close to exposing the actual strengths or limitations of a given framework.

elchief 14y ago

"Set the bar so low, no one cares if you succeed" - Homer Simpson Something like Google contacts, or Gmail if you wanna push your luck, would be more appropriate.