[pbiggar]

> mostly a concern for folks who already know how to code, who wouldn't necessarily use it anyway if that specific blocker were removed

Yes, I think that's right. There's a lot of folks who have strong feelings about this but who aren't necessarily our target user. I know that's going to cause a lot of problems but what can you do :-/

> I guess another option would be having Dark function more as an app-store-like intermediary between the hardware and software.

Yeah, this very much isn't what we're trying to build, or the business we want to be in :)

> In terms of a community, I guess I meant more in terms of getting developers to create libraries for data processing

Gotcha! Yes indeed, there will be a package manager very much like npm/cargo/rubygems, for just this sort of thing. We plan to make it extremely easy to create and share packages.

[Alex3917]

> I know that's going to cause a lot of problems but what can you do

That's a good point, in the sense that even if less technical people don't care about certain issues, they're often not going to adopt the product without first soliciting advice from people who do care about those issues. So that just means potentially needing to build out a lot of stuff knowing that people won't actually use it for a long time.

Sort of like our product and the OAuth issue, which we're finally on track to (mostly) solve with a Gmail add-on but it's obviously been several years at this point.