The real pace of development of EOS
This is a direct response to the irresponsible journalism from this article from Yahoo Finance. I am loathe to push traffic their way, but I think it is a valuable place to start a discussion from.
We at Scatter believe in facts, data, and investigation.
To start, we need to present the original, problematic content from Cryptomiso’s EOS chart
Commits to a single repo do not an ecosystem make
The fault in logic here is glaring and shameful. Tracking a single repository’s commit history does not actually tell you anything about how EOSIO is progressing because EOSIO is not just one repo.
There have been over 600 commits on EOSIO repositories over the past month alone. EOSIO/eos was split into multiple repositories to create better separation of concerns and more maintainable code. This is a good thing that makes a codebase more manageable! Most of the work is done on other repositories now, an initiative which started quickly after the mainnet launch.
A quick glance at the EOSIO organization GitHub and a tally of the commits on the top repos takes about 2 minutes tops, and completely disproves this article. I’d imagine the same lack of investigative journalism is present across the board there and the people at Yahoo Finance should be more careful about what they post without vetting their sources first.
Each of the following repositories are crucial parts of the ecosystem. Some are pieces of the chain itself, one is the system and default contracts that run on the chain (
eosio.contracts), some are for development purposes like
eosjs and some are global helpers like
abieos. The data below is for the past month (February, 2019) alone.
You might also notice that commit density doesn’t correlate to code additions and removals. This is the nature of development. Sometimes we sit on branches locally while doing things and only push up when necessary. Normally, commit bloat occurs when developers push smaller changes into a repository to fix small bugs and such (like when closing tickets), and not when developing new features.
demux-js is a good representation of that. Less commits than
eos, but far more code changes since it just went under a small overhaul. Notice that
eosio.cdt has no master code modifications either, which means that they are working on a new branch (which happens to be a
1.6.x branch, probably aligning to recent
eos tag), meaning there's a whole new stable version being worked on.
We urge Cryptomiso to update their methodology, and for CCN and Yahoo Finance to issue retractions.