That is exactly why i am trying to build up a case against it. I would not have been so worried if the closed source component was just a small module in a larger OSS product...in this case we are talking about a complex db/storage software...which probably every component in the larger product is gonna interact with.
The developers seem to know what they are talking about. I have looked at the source (not all, since there is a lot) it seems properly documented. But maybe not enough, if someone independent wants to start maintaining the thing by themselves (and I dont think that is even being considered !) The additional functionality is largely at the application level where the other product has readymade functionality, which needs to be developed on berkeleyxmldb.... > > > Good lord. For something so horrendously evil, I'd insist on reading the > source for the commercial product before making up my mind (and figure > out how I'd feel about maintaining the whole thing myself, because that > might be the ultimate result of the various disaster scenarios people > have proposed). And its lack of documentation wouldn't exactly endear > it to me. > > Have you read the source? Spoken to the developers? Are they clueful? > > (BTW, I'm curious. What is it you need that is only half-implemented in > Berkeley DB?) > > -- ams >
