I’ve been researching technical aspects of Cardano a lot this week. The roadmap raised a good point:
“First, we can only grow as fast as our community. At the moment, more than half of our community has never used a cryptocurrency before. This reality means that while it would be awesome to introduce complex features like stake pools, blockchain based voting and subscribable checkpoints, they would be underutilized and therefore ineffective until the community catches up.”
For me, it has been a complete whirlwind from the K framework, Daedalus wallet, IELE, Cardano-sl…
It appears impractical for me to spend my time contributing to a project that is out of my league. That statement was not a complaint, it represents my effort to contribute to the community but the depth involved for my contribution would probably not qualify for a merge or code review.
Maybe it would be best if I stay on the sidelines of Cardona until it evolves a little bit more.
@io_jeremy mentioned an explorer for Daedalus, creating a custom wallet that calls API with Cardano in another post. Does this mean a JAVA or .NET developer create their own wallet project? Does Cardona create a developer key for api calls? Other than the Daedalus project or if developers know Haskell or similar functional programming languages, the developer community appears to be small.