Earlier quoted context omitted.
This is the typical argument on a very technical board such as HN where blockchain is synonymous with a specific implementation. But that's an outdated way to think about blockchains. Yes, Bitcoin's implementation is a huge resource hog and slow. But for most newer projects "blockchain" just means an auditable trail of state changes. Whether you implement this with the shiniest newest db paradigm or some simple SQL d…
Then we, as engineers, have failed in explaining things. A blockchain is a linked list where each element of the list contains the hash of the previous element. It's basically a degenerate Merkle tree. That is all that it is. It isn't a metaphor. It isn't throwing off the shackles of an overreaching government, nor is it a takeover of our society by militant right-wing conspiracy theorists. It's a data structure.
> The first blockchain was conceptualized by a person (or group of people) known as Satoshi Nakamoto in 2008.
So "degenerate Merkle tree" is not enough, it also needs consensus mechanism, byzantine failure tolerance and so on.
Insisting on meaning of "blockchain" which is different than commonly accepted will just make all arguments more confusing.