3 ms·
I'm sure there are a few problems with this analysis that people smarter than I can point out but one thing that does come to mind is the age of a repository. I
by SirSavary 9y ago
I'm sure there are a few problems with this analysis that people smarter than I can point out but one thing that does come to mind is the age of a repository. I'm fairly confident that most of the highly starred Java and C++ repositories are much older than the ones for other languages. I'm not sure if the graphs took age into account but if they didn't, they should. A library that's been around for 10 years will likely have more than one that's been around for 1 years so it's not really a fair comparison.
- marcus_holmes 9y agoThis is a good point. Maybe measuring bugs/year instead of bug count total would work better. Of course, what you want is all your bugs to be discovered quickly. It'd be interesting to see the bug/year count across all projects for each language, too. I suspect dynamic languages are prone to "coping" with bugs for longer, until a broken edge case is discovered.
- concede_pluto 9y agoI found myself wondering whether the paranoid mindset that finds static typing reassuring is more likely to realize when code doesn't work.