You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 29, 2021. It is now read-only.
As discussed in other issues the Dat ecosystem is hard to discover by newcomers. This due to:
Dispersed repositories, and - to lesser extent - documentation
Docs mainly details dat-node, hyperdrive, hypercore, hyperdiscovery, and just a couple of links to other package repo's
So I took some time to turn this into a chart:
Its incomplete, of course (e.g. forgot to comb awesome-dat), and there are a lot of other community packages floating around.
Supported / official modules
If you consider dat, dat-node, dat-js and dat-desktop to be the 'product line' of the Dat Project, then all green modules must represent the 'official' modules of the ecosystem. The core modules.
This because they are (transitive) dependencies of these projects.
Optional / sattelite / misc Dat Project modules
In orange the modules that are satellites to the core ecosystem, that are optional, or are apps, misc or abandoned projects created by the core team (except the orange '(many others)' category, which represents the wider community.
Important external packages
Non-Dat modules that are depended upon to implement vital technical concepts in the Dat architecture. The list is incomplete.
Conclusion
IMHO the official Dat Core ecosystem is indeed fragmented and confusing, and would benefit much from a cleanup. With current structure you do yourself a disservice when others don't discover the cool things you do.
The text was updated successfully, but these errors were encountered:
As discussed in other issues the Dat ecosystem is hard to discover by newcomers. This due to:
dat-node
,hyperdrive
,hypercore
,hyperdiscovery
, and just a couple of links to other package repo'sSo I took some time to turn this into a chart:
Its incomplete, of course (e.g. forgot to comb awesome-dat), and there are a lot of other community packages floating around.
Supported / official modules
If you consider
dat
,dat-node
,dat-js
anddat-desktop
to be the 'product line' of the Dat Project, then all green modules must represent the 'official' modules of the ecosystem. The core modules.This because they are (transitive) dependencies of these projects.
Optional / sattelite / misc Dat Project modules
In orange the modules that are satellites to the core ecosystem, that are optional, or are apps, misc or abandoned projects created by the core team (except the orange '(many others)' category, which represents the wider community.
Important external packages
Non-Dat modules that are depended upon to implement vital technical concepts in the Dat architecture. The list is incomplete.
Conclusion
IMHO the official Dat Core ecosystem is indeed fragmented and confusing, and would benefit much from a cleanup. With current structure you do yourself a disservice when others don't discover the cool things you do.
The text was updated successfully, but these errors were encountered: