When two devices write to the same field, the update with the latest timestamp wins.
I’m confused. That update is not conflict free. It resolved the conflict by deciding one of the two wins, without resolving the underlying difference (add and subsctract must be combined/summed up).
Most systems ask developers to write manual conflict resolution code, but that’s error-prone and hard to maintain.
In my eyes, we resolved the difficulty by ignoring correctness.
Surveillance Capitalism.
Well yeah this is the obvious drive-by comment, but there are good technical reasons too,
which you might understand better if you had actually clicked on the article, which of course you didn’t,as probably didn’t most of your drive-by upvoters.Ah, social media. Sometimes I wonder why I bother.
I read the article. It says it’s actually pretty easy to solve (I disagree with last write wins, especially given their example, but it’s pretty simple to implement), and doesn’t talk about capitalism at all.
The answer to the headline is just capitalism. It’s not technical difficulty, and this didn’t need a whole article. Every developer already understands this. It’s just not a business priority.
