%nVcXM0z/ZGY6AcD+RN/74n74KTrMEIfkZqPytsSZi2U=.sha256@dinosaur it's not a choice between patchcore and patchless - there is lots of stuff that uses sbot client directly, eg, patchfoo or git-ssb.
yeah totally. i agree that providing high-quality documentation for the modules in common is the best strategy. i hope patchcore and patchless converge in time with a re-write anyways.
more subtext: i'm also thinking about the target audience who aspires to be an ssb application developer. so far i think we as ssb developers have prioritized making it work, with less regard for how a typical enterprise / web application developer who has only seen traditional patterns and code styles will perceive our systems. i see patchcore as our first direct attempt to address this problem. we tried our best, but it's still confusing as hell for any newbie, wow! what i'm saying is i want to support more efforts in the direction towards an enterprise-level stack suitable for your average developer, by continuing to refine our systems with better documentation, standard code style, dry code architecture, less footguns, etc. so i find it hard to endorse application developers being guided towards what i perceive as making it work and not trying to cater to average developers with traditional mindsets. more directly, i've witnessed far too many people struggle to understand your code @dominic, or seeing @mix in pain trying to refactor code in git-ssb. i think what we've done so far is wonderful, i wouldn't take anything back if i could, but i'm interested in how we evolve from here towards the next step of potential contributors. or maybe i'm totally in my own world, that's entirely possible, but in my defense i pair with more junior developers as my primary paid work. 