I’m not saying I agree with 100% of the above quotes, some of it may also depend on what area you are working in, but I do at least agree with elements of it. Had a similar discussion on Reddit recently asking about hackathons for developer tooling.
On the one hand, its great to see so much effort and research being put in to keep the blockchain tech top tier, and making sure we have the right pieces in place to scale. We’ve shown the world that we can upgrade huge chunks of the chain, and bring in massive new features / changes.
On the other, its frustrating to see new feature + new feature + new feature coming from the core team, while such critical stuff like local forging, michelson SDK’s, wallet creation, encryption, formatting, hashing etc is left up to the community to build from scratch over and over again in different languages.
A post from nomadic went out a few weeks back, talking about all the new layer 2 stuff that will be added in coming protocols. Don’t get me wrong, that all sounds very cool and super useful … but do we need it right now? is increasing the scalability such a massive priority that it needs to be all hands on deck? Personally I don’t think so. I’m writing Swift code for Tezos at the minute and I have to rely on Trust Wallets open source library (which is massive, and incompatible with MacOS for writing desktop apps) in order to create private keys and wallets. I spent days researching how to convert a module of Taquito into something that I could put into an iOS JSContext, so that I can perform local forging. Not only am I hoping that a third party team have duplicated the client code for local forging perfectly, i’m also hoping they maintain it, and I have to manually check for updates and pull them down because its not compatible with my code in its current form. Running through JS also comes with a noticeable performance hit.
I firmly believe the core teams taking a break, and making some of the internals of the client/node available as standalone modules (in C, C++, Rust etc) that all languages can import, is a far more important task than some of the current ongoing upgrades. Dealing with Tezos means dealing with a lot of highly custom, bespoke or advanced topics. I’m not a cryptography guy, I don’t have a degree in computational linguistics or high performance programming. I come form a much more simplistic, higher level / frontend / UI+UX, style of background. Having to spend weeks and months digging through all this stuff is a massive burden. When the Edo protocol was announced that it would be making changes to Michelson, that was extremely costly to teams. There was no tooling or SDK’s provided, only written documentation and example contracts on testnet. Every team had to stop what they were doing and research this new topic and test the hell out of it.
The developer community needs the experts that are building all these core critical features, to make them available, ensure they are maintained, and updated before any proposal is injected. Too much is being expected of the developer community. It feels like the core teams are too focused on the Research aspects of development, and less so on the more production side of things