Quote from: WiW on March 12, 2013, 04:25:29 PM

The events occurring due to the update from 0.7 to 0.8 show, in my opinion, that client decentralization is just as important as node decentralization. Notice that I don't even have to say which client I'm talking about. It's obvious we're all using the same client.

Don't get me wrong, the devs for the open source client brought to us by the foundation are doing an excellent job and I salute them. I have no doubt that the core devs have no malicious intent, but as bitcoin matures it is important that there be no one entity which mediates the protocol. There have been talks about how a client sitting on the majority of nodes which auto-updates from a single source could be hazardous to bitcoin - not only with regards to bugs, but also by malicious intent. In my opinion, it is very important that as bitcoin matures, we have a consensus on how to implement the protocol and not a faucet that showers on us how to implement the protocol.

I have been quite disappointed with the variety of clients available. Yes, there are plenty of clients which satisfy a multitude of needs and desires, however I still feel like there need to be more. Not only with full nodes, but also for noob-friendly and merchant-friendly clients. If we are to go the linux way, only insiders will be satisfied and there won't be enough effort to get more people involved. For example, just the other day I wanted to print air-gapped paper wallets in bulk and was surprised to discover that there was no "bootable, ready-to-start-printing, bulk private key generator live CD". Maybe that's asking for too much, but the fact is that the best way to make private keys in bulk for the average user is with bitcoinaddress.org (you know, the one that works in your internet browser).

I, as one who is in the process of studying programming and software engineering, plan to write at least one open source bitcoin client (and hopefully other bitcoin-related software as well). I hope more heed this call.

This event proofs that it is basically impossible to re-implement the Satoshi client. You not only need to re-implement all functions and features, but also all bugs, in order to be compatible with the Satoshi client. Making a incompatible will just lead to a hard-fork like this event.