Why did IPFS made way for KUBO and discontinued earlier method via go-ipfs ?

KUBO is a new project by Protocol Labs, the same organization that created IPFS. While IPFS is a great tool for decentralized storage and content addressing, it still has some limitations when it comes to scalability, performance, and interoperability. In particular, IPFS relies on a single node to manage the content of a particular hash, which can be a bottleneck in a large-scale decentralized system.

KUBO, on the other hand, is designed to address these limitations by using a sharded architecture that distributes the storage and retrieval of data across multiple nodes in the network. This allows KUBO to scale more effectively and handle larger volumes of data with higher performance. Additionally, KUBO is designed to be more interoperable with other decentralized technologies, which makes it easier to integrate with other decentralized applications and networks.

As for why the earlier method via go-ipfs was discontinued, it's likely because Protocol Labs wanted to focus on developing KUBO as a replacement for IPFS. While go-ipfs is still an actively developed project and remains a popular implementation of IPFS, it may not have the scalability and performance capabilities that KUBO promises to deliver.