Very good point. I never thought about it that way.
I have been criticizing them for their default settings (no response to write requests, safety turned off by default) for a while.
But actually it is not as much for settings themselves, but for lack of a clear red flashing warning on their front page. As their default settings could (still can?) lead to silent data corruption. The worst possible thing to happen to a database. That is shady and shitty practice if you ask me.
They are trying to market their technology to other developers, I expect them to at least try to be honest and open about the characteristics of their product. If they treat other developers like they are customers for male enhancement pills in 4am commercials, then I think they should also expect some backlash from said developers when they choose Mongo and then hit all the hidden assumptions and un-delivered promises.
Sure it is in the fine print. But if it is important, why not put it in the big print. It is a lot less painful for everyone in the long term.
I have been criticizing them for their default settings (no response to write requests, safety turned off by default) for a while.
But actually it is not as much for settings themselves, but for lack of a clear red flashing warning on their front page. As their default settings could (still can?) lead to silent data corruption. The worst possible thing to happen to a database. That is shady and shitty practice if you ask me.
They are trying to market their technology to other developers, I expect them to at least try to be honest and open about the characteristics of their product. If they treat other developers like they are customers for male enhancement pills in 4am commercials, then I think they should also expect some backlash from said developers when they choose Mongo and then hit all the hidden assumptions and un-delivered promises.
Sure it is in the fine print. But if it is important, why not put it in the big print. It is a lot less painful for everyone in the long term.