3 ms·
"""Duplication of effort is a non-problem,""" Really? Because of I've been following OSS communities for, like, 15 years, and it has been a huge problem in mos
by dextorious 15y ago
"""Duplication of effort is a non-problem,"""
Really? Because of I've been following OSS communities for, like, 15 years, and it has been a huge problem in most of them.
- malandrew 15y agoDuplication of effort leaves more room for experimentation, so it's not all bad. If there was only one canonical version of all modules, it would be very limiting. For problems that are deemed solved or community issues, having one or canonical module is great. A good example of this is JSLint and JSHint. For problems that at TIMTOWTDI, duplication of effort allows exploration of the problem space. Once the right location for the new hive has been found we'll just headbutt the other worker bees into submission :P
- dextorious 15y agoI agree -- I was basically answering the parent that it's a "non problem". Sometimes it IS a problem.