Hacker News new | ask | show | jobs
by x-complexity 1057 days ago
For me personally:

When architected correctly (as with pretty much all software), it allows for a service to live (effectively) forever, independent from the creators of the service.

Example: I create a smart contract where everyone can post an IPFS hash to it, with added functionality to be able to post on someone's behalf if they give a signature to do so.

(This simple example is deliberately chosen to be a starting point. More complex functions & services can be derived from this starting point alone.)

If I were to kick the bucket, or if I'm not capable of contributing to its development, the service is still accessible to everyone else. If someone else wants to keep developing the service, they can do so via the contacts defined endpoints.

To me, the positives of this starting point outweigh the technical complexities involved with its development & maintenance. It varies wildly for others, but for me, this is the anchor point from which I can build something that can last long after me.