in reply to Re: On collaboration between projects
in thread On collaboration between projects

The existence of several similar solutions to the same problem is not necessarily bad, it allows for in-depth exploration of a problem-space and means that users can use a solution that's most to their liking. - I count that as one of the, mentioned by me, 'technical reasons' :)

But when reading that, I just had that thought that it is actually more breadth-first exploration - while forcing to collaborate on one solution would be depth-first exploration.

  • Comment on Re^2: On collaboration between projects

Replies are listed 'Best First'.
Re^3: On collaboration between projects
by tirwhan (Abbot) on Feb 19, 2009 at 09:49 UTC

    This is rather abstract to discuss without a concrete example, but you need to have breadth and depth both, don't you? Having x modules all do the same task with different interfaces will shake out the "most preferred" over time or it will result in multiple interfaces existing to suit different types of people.

    Again, collaboration is good, and for these modules to eventually use the same "engine" under the hood could be a good thing. Even though that model of development (create differing solutions and then try to cobble them together) appears to be ass-backwards and more work, it seems to work pretty well.


    All dogma is stupid.