I don’t want to distract the core team, but I also want set expectations of where we are and where we are going. Which even in present tense is still a lot of changing and new concepts being introduced but only documented by being stated in a dev update blurb.
So lets take this exchange for example:
Every time I try to talk about SAFE I will ask: So how does X accomplish Y. Then I get “well we solve it by doing Z and T”. And I will be curious where the solution is in code that implements Z and T. And then I try to find in code or docs etc and its not easy to know where everything lives. Or the concepts that are almost talked about as if they are commonplace and complete, such as malice are actually still TODO and have not been dealt with, see:
https://github.com/maidsafe/parsec#upcoming-features
for example. It seems lots of core concepts have onions to peel back in dialog to get to the core of how it works and in many cases I struggle to see the high level concept 100% fleshed out all the way to the bone in implementation. I guess that is where my frustrations lie. We have too many high level concepts and I can’t see full v1 implementations in many of the components(UI components are usually self-evident but more talking backend + network components). Hence I want an SLD and tech specs that hopefully link out to source and also gives an idea of whats actually left to implement vs whats been fully baked and doesn’t need touching anymore.