I'm glad the dat cli is still working for you. It's on an older protocol codebase and won't be maintained, the hyp cli is meant to replace it going forward.
If someone would decide to use either dat or hyper as a base for a project today: what are the differences?
Is hyper going to replace dat as an advancing network protocol? Is peer discovery different, or did hyperdrive change...or...?
(I am very confused about dat/hyper efforts, as I've been following it a bit over the last year)
I've seen that beaker changed to hypercore/hyperdrive...so my current assumption is that the hyper protocol is the web browser effort, rather than the other parts of infrastructure.
Are there incompatibilities in both protocols, or is hypercore trying to refactor its codebase in order to say, remove legacy dependencies that might not be necessary anymore?
Dat is essentially the old version of Hypercore Protocol (aka "Hyper"). We had to make a set of breaking changes and decided to rebrand. So- if you're looking for a base, use the hyper stuff.
The changes included a switch to a DHT for peer lookup and data-structure reworks that improved speed and scaling by quite a bit.
Does the new cli allow multiwriting yet? I'd like multiple computers to be able to modify the dataset.
Similarly, it seems the protocol supports keeping around all versions of the hyperdrive, but it looks like that isnt made available via the cli. Is this correct?
Is hyper going to replace dat as an advancing network protocol? Is peer discovery different, or did hyperdrive change...or...?
(I am very confused about dat/hyper efforts, as I've been following it a bit over the last year)
I've seen that beaker changed to hypercore/hyperdrive...so my current assumption is that the hyper protocol is the web browser effort, rather than the other parts of infrastructure.
Are there incompatibilities in both protocols, or is hypercore trying to refactor its codebase in order to say, remove legacy dependencies that might not be necessary anymore?