You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to see some type of performance comparisons between all of the options out there. Like speed tests between adding one, deleting one, deleting all, mark all as done, or initial rendering of a really long bootstrapped list of todos.
Although I am imagine in these really simple examples the differences would be almost negligible except for perhaps the rendering of the big list (which is also dependent on the template technology being used). In more complex and data-intensive apps those figures might actually add up to something significant.
Also, and this one it probably really easy to do- maybe in the documentation there could be some chart of the different file sizes the whole package comes out to, maybe without and without dependencies included.
I know the most important things when comparing these apps is code style and robustness, but I think some other comparison charts might also weigh in on peoples decisions. Keep up the great work! Thanks for this great resource!
The text was updated successfully, but these errors were encountered:
@dannyc I think that's a good idea. It will probably have to wait until after version 0.3 has been released for me to look at, but I recall Brian LeRoux doing a TodoMVC based file-comparison (figures here: https://gist.github.com/1222220). Will put it on my todo list!
@sindresorhus I kinda feel like at the Todo app level these performance comparisons would be relatively micro in difference and would offer negligibly useful value. What do you think?
It would be nice to see some type of performance comparisons between all of the options out there. Like speed tests between adding one, deleting one, deleting all, mark all as done, or initial rendering of a really long bootstrapped list of todos.
Although I am imagine in these really simple examples the differences would be almost negligible except for perhaps the rendering of the big list (which is also dependent on the template technology being used). In more complex and data-intensive apps those figures might actually add up to something significant.
Also, and this one it probably really easy to do- maybe in the documentation there could be some chart of the different file sizes the whole package comes out to, maybe without and without dependencies included.
I know the most important things when comparing these apps is code style and robustness, but I think some other comparison charts might also weigh in on peoples decisions.
Keep up the great work! Thanks for this great resource!
The text was updated successfully, but these errors were encountered: