On the Switch playing Mario Kart 8 with a 5 and 3 year old is everything I wanted. It can both be cooperative and competitive. We have also ventured coop through Mario Odyssey. I think Minecraft is fun, but you definitely have whole bunch of games you should explore with the kids.
Moreover, "bugs" can linger around in code for a long time and you can't really track that metric. Code changing over time in a repository could be to fix bugs or refactor/rewrite etc. I think the original posters question was more around whether there are existing resources to track these things to which the answer I feel is no. Combining blogs posts, stack exchange score, speaking topics and other real world things can give you some semblance of a developers engagement with the development community but doesn't translate one-to-one on their actual productivity levels on a team. Although these things usually indicate a greater potential for success.
I will post this here as well for posterity. I appreciate the time you took to compare and contrast the frameworks and your article is very thorough. We started with backbone on a few large projects and found angular late. We have switched to using angular where ever possible given the reduced code and testability.
I think another good comparison to make that is missing from both demo application stacks is testing. It becomes increasingly difficult to test backbone with the side effects of having jQuery selectors, html elements and general DOM operations directly in your view models. One of the great advantages of angular is it's attempt to make invert your thinking about dom binding compared to other frameworks. Meaning it tries to keep the DOM and the MVVM separated so there aren't unintended side effects if you add or change html node ids or classes. Backbone more tightly couples you to a specific html model and makes testing your javascript code complex and coupled to also looking for changes to the physical DOM during tests.
In the end, the more complex problems see to cause equal headaches in both frameworks, but at least angular give you less lines of headaches.
Just on the surface the potential for the minified library with its reduced size and browser support sounds great. In just checking a few features it seems as though the performance doesn't line up with jquery atm. In a large application space would I rather trade off js performance for saving initial DL time (cache)? I start to wonder where diminishing returns set in, if I should I really care about IE6 anymore or if the clean and simple API you say won't change will in fact never change.
I think they were trying to keep the hash sizes to ~1000 elements each key. At a 3 digit key you would be increasing the hashes to 300k elements each. You should augment the scripts and see if that has an impact on the performance, would be curious to see.
I would like to see some example code or a gist of what you did. I played around with custom number packing and using the hashset in redis inspired by the original thread topic and your comment. You can find the post here: http://www.christianoestreich.com/2011/11/redis-hashsets-per...