| It's more of using specialized, purpose driven applications vs using a generalized swiss army knife of epic proportions. Handshake was purpose built to work with traditional DNS while ENS is something entirely different. I think that's why Handshake is gaining more adoption in the traditional DNS sector as well, but whatever the case, I've opted to work with this technology based on a number of factors: 1. The ENS project is great for creating human readable Ethereum wallets. However, it doesn't seem that it was initially suited to be used for DNS and that this was later patched on. 2. ENS is centrally controlled by a federation of key holders [1] while Handshake is decentralzed. 3. In Handshake, you truly own the name. 4. With blockchain already inheriting many inefficiencies when compared to more traditional systems, ethereum, while very cool, tries to be too much and the bloat has led to extreme fees for interacting with the blockchain. That being said, I'm keeping my eye out on all of the naming projects. It's something I'm very interested in. [1] https://docs.ens.domains/frequently-asked-questions |