3 ms·
I took the opposite route in 2010, and it didn't work out well for me. We sold it as a premium product, and it was hard to get adoption. Which made it hard to a
by jfengel 6y ago
I took the opposite route in 2010, and it didn't work out well for me. We sold it as a premium product, and it was hard to get adoption. Which made it hard to actually prove the benefits we claimed should exist.
That's not proof that we'd have fared better if we had open-sourced it. We took exactly the opposite route of MongoDB, with very stringent schemas to ensure data quality. That required a large up-front investment in time, and that was a hard sell too. The whole world went in the opposite direction, of schemaless databases and machine learning for "eh, good enough" answers.
Still, I'll always wonder if we wouldn't have failed so spectacularly if we'd open sourced it. The idea was a pretty good one, and we wrote some remarkable software to make it happen.
- 3np 6y agoWhat is the "it" you're referring to here?
- jfengel 6y agoThe company was called Highfleet. We built ontology-based databases. Not OWL ontologies; we were actually doing ontologies before OWL. We were briefly and tangentially involved, but we thought they had picked the wrong level of ontology. We had a full-featured logic language for really strong definitions, so that you have strong guarantees about data quality and good ways to reason about data integration between databases. In the end we never found the right use case for it. The advantages were all in maintenance rather than development, and even people who could be talked around to it wouldn't see the payoff. There were a trillion other problems, and maybe better management than me could have made it work.