4 ms·

You can't misuse closed source APIs? How would you know something is O(n) without seeing the source code?

• snowwrestler 12y ago
  I wondered the same thing too. I think the answer is here: > people using closed source will start delivering faster and faster as they effectively partition the review/quality question to the person selling them the software I guess the theory is that if you have a customer/vendor, contractual relationship, then you can task the closed-source vendor to describe, fix, or alter their API. But my (albeit limited) experience is that the customer is not always right; sometimes the vendor just says "that's the way it is" and you're stuck either living with it or porting to a different company/technology. Conversely, it's often possible to hire a vendor or consultant to provide expertise and support for some aspect of an open-source stack. And because it's open-source, if you don't like your consultant you can go find another one without having to change your technology. In short, I think the speed of innovation thing might have more to do with internal teams trying to manage too much diversity of technology, than with some inherent shortcoming of open source.