3 ms·

I've been following the Dat story for a few months, Congrats! What do you consider to be THE killer feature(s) of Dat over the classic web? instant Publishing?

I've been following the Dat story for a few months, Congrats! What do you consider to be THE killer feature(s) of Dat over the classic web? instant Publishing? Resilience?

pfraze 6y ago
Personally I think it's the hackability. Data is disconnected from apps (in your personal drives) and shared between applications. Hyperdrives are also forkable. Beaker currently pushes people to create personal sites and build social applications around that. I think a very open social/identity system is just very cool. There are also some things that are much easier than they normally are - for instance, you can setup a webrtc call using PeerSockets, so you don't need to setup a server to do that. The "zero devops" story is pretty nice.
- sylvain_kerkour 6y ago
  So if I understand right: Hyperdrive (formerly Dat) is the "p2p platform" and beaker a client which uses hyperdrive to publish and browse archives and websites? If I want to build an app using this, when should I choose hypercore and when should I choose hyperdrive?
  - pfraze 6y ago
    Currently Beaker only has Web APIs for Hyperdrive, but we're going to add Hypercore APIs Hypercore is lower-level - it's basically an append-only log. There have been some projects that use it directly such as Kappa-core [1]. You might want it particularly for CRDT work, but generally I think you can use the filesystem to do pretty much anything, and that has the benefit of a regular data-form that can be explored using the terminal and files explorer and browser and etc. [1] https://github.com/kappa-db/kappa-core https://github.com/kappa-db/kappa-core
    - sylvain_kerkour 6y ago
      Ack, thanks!
- sylvain_kerkour 6y ago
  Also, I love the "zero devops"! It's not a popular opinion but I really believe that once this kind of protocol will be more mature / have some success stories, the cloud mania could disappear as fast as it appeared!

I've been following the Dat story for a few months, Congrats! What do you consider to be THE killer feature(s) of Dat over the classic web? instant Publishing? Resilience?

pfraze 6y ago

Personally I think it's the hackability. Data is disconnected from apps (in your personal drives) and shared between applications. Hyperdrives are also forkable. Beaker currently pushes people to create personal sites and build social applications around that. I think a very open social/identity system is just very cool. There are also some things that are much easier than they normally are - for instance, you can setup a webrtc call using PeerSockets, so you don't need to setup a server to do that. The "zero devops" story is pretty nice.

sylvain_kerkour 6y ago
So if I understand right: Hyperdrive (formerly Dat) is the "p2p platform" and beaker a client which uses hyperdrive to publish and browse archives and websites? If I want to build an app using this, when should I choose hypercore and when should I choose hyperdrive?
- pfraze 6y ago
  Currently Beaker only has Web APIs for Hyperdrive, but we're going to add Hypercore APIs Hypercore is lower-level - it's basically an append-only log. There have been some projects that use it directly such as Kappa-core [1]. You might want it particularly for CRDT work, but generally I think you can use the filesystem to do pretty much anything, and that has the benefit of a regular data-form that can be explored using the terminal and files explorer and browser and etc. [1] https://github.com/kappa-db/kappa-core https://github.com/kappa-db/kappa-core
  - sylvain_kerkour 6y ago
    Ack, thanks!
sylvain_kerkour 6y ago
Also, I love the "zero devops"! It's not a popular opinion but I really believe that once this kind of protocol will be more mature / have some success stories, the cloud mania could disappear as fast as it appeared!