|
|
|
|
|
by treelovinhippie
3944 days ago
|
|
The TCP/IP equivalent layer: https://ethereum.org The WWW/browser equivalent layer: https://www.youtube.com/watch?v=IgNjs_WaFSc Done. *at least as an awesome starting point. The easier it is for developers to build on the platform and the more network benefits/incentives that arise, the more high utility Dapps will be deployed, the more likely Chrome/Firefox/IE will integrate seamless DNS/pointers to the Ethereum platform. The web will become decentralized by default and the average user won't even notice. And I mean "platform" in the sense here of a distributed blockchain or lower-stack layer, not some corporate-owned data silo built on proprietary API endpoints and protocols. |
|
But with apps I personally want to make, I'm more interested in MaidSafe Network. It's basically a distributed data storage network, fast enough that it's good for communication/message passing in apps.
MaidSafe got me interested in making apps for it that are pure client-side JS, with the intention of them being served from the distributed storage. While I dislike running JS in the browser, I will support it when it means there's no server. For now, my intention is to write apps using the Elm language.
Other interesting work continues to be done in Tahoe-LAFS, I2P, and Freenet. There's also IPFS. I'm looking forward to the future of this tech!