On 26 Nov 2013, at 16:07, cbullard@hiwaay.net wrote:
The politics will obscure yes, still there are some clues:
1. MarkLogic is being blamed with the statement that having XML is
in the database is apples in the orange bin.
What I've sometimes seen on projects like this is that a decision is
made to use some technology, and then it isn't followed through. They
buy the software, and they use it, but they aren't committed to it,
or they try and hedge their bets. Someone discovers, say, (no idea if
this is true) that there's a feature in the product that allows them
to use SQL, and that's what they know, so they do everything in SQL,
and no-one tells them that if they're going to do everything in SQL
then MarkLogic isn't really designed for that. This happens very
easily when the technology decisions are made by people with no
contact with the actual developers, who may even hate the guts of the
people who made the technology decisions and be determined to prove
them wrong or to get the decisions reversed. That can be because of
commercial factors (subcontractors competing for a bigger slice of
the pie) or simply personal cussedness: developers don't like being
told they can't use their favourite technology.
