6 ms·
"# of users" is a metric I use to choose which framework to use. For one, it makes it much more likely that a problem I'm having can be solved with a google or
by dsil 14y ago
"# of users" is a metric I use to choose which framework to use. For one, it makes it much more likely that a problem I'm having can be solved with a google or forum or stackoverflow search.
I think that alone makes it a much better metric to judge the experience you'll have with a framework than its cyclomatic complexity (at least for a user of a framework, maybe not as a developer)
- raylu 14y agoA bit off topic here, but I feel that this is a terrible metric. The reason it's impossible to find answers for how to fix problem X in Windows (besides it being terribly designed) is that there are a ton of users who are trying to be helpful and providing bad advice. Googling for solutions to an Ubuntu problem is starting to look grim too. Read some bug reports on Launchpad and then read some on the Debian bug tracker; there's a clear difference in signal/noise. Circling back to the original point: if a web framework is simple, you can figure out the problem by just reading the code rather than looking online for solutions (many of which are in the form "oh, framework Y automatically does Z for you so you have to...").
- mattdawson 14y agoI don't care how simple a framework is. There are always dusty corners that are hard to understand. There will always be bugs. And the ability to get help from fellow users when you hit those is, in my experience, crucial.
- jarcoal 14y agoBy "problem" the OP didn't just mean a bug or ambiguous situation, they meant plugins, addons, etc, that the community has contributed. EDIT: Reading his post again, maybe he didn't mean that, but the point is still valid.
- bthomas 14y agoDon't forget ease of finding and/or training other developers to work on a project