Of course. To say one isn’t to concede the other. I think the major trade offs mostly happen at the protocol layer, which much of those issues are being solved very well, it’s simply about extending them up to those who can use them properly. 

Again nsec bunker like tools are a great example. Literally all of the tools are there, it’s just never been made intuitive and the edges haven’t been cleaned up. And if that doesn’t happen then there’s no demand from clients to support it. Circular problem.

I think it’s less of a problem of trade offs for a lot of these, and more a problem of people excited to build a tool that they can use, but not interested in building it for someone who doesn’t understand anything about it. Devs I think get lost in chasing the next awesome thing, rather than doing the slow, difficult process of making the last thing built really streamlined, intuitive, and reliable.

Not saying I am not guilty of the same. It’s like building a house but never painting it or putting up trim. It’s just the annoying part of building because it’s slower and it feels like progress isn’t moving at all. But it makes all the difference in the world from the user’s perspective.

I also don’t think we should depend on the devs to do this. I think we need “another layer” of developers, who work with this stuff and try to clean it up for the regular user.

Part of the direction I’m trying to take our team is related to that. Hoping I can help, but I also know how much harder it is to get it done vs *wanting* to make it happen.