I don't think that was the point of the article at all. The point is that distributed systems engineers know already about these sets of tradeoffs, and many of

I don't think that was the point of the article at all. The point is that distributed systems engineers know already about these sets of tradeoffs, and many of the alternatives to them, and with that wider perspective see few, if any, reasons to recommend blockchain. Meanwhile many the people going around hyping up blockchain know very little about the tradeoffs and alternatives, and are definitely _not_ recommending blockchain because it's the right set of choices in each of the tradeoffs. Like - picking randomly - KodakCoin[1], he would argue (and I would agree), definitely did not choose to use blockchain because was the database that made the most sense for their needs. Indeed, it's probably a terrible choice compared to the alternatives. (Except, perhaps, for optimizing for"hype factor" as seems to have worked considering their stock price, in which case the best thing to do might actually be to lie and _say_ you're using blockchain, and then... not.) [1] https://en.wikipedia.org/wiki/KodakCoin https://en.wikipedia.org/wiki/KodakCoin