Publishing some notes from the call here.
aragonCLI was broken
This is not even related to aragonCLI itself, but probably to one of its dependencies. Dependencies break often, and it definitely feels like building a sand castle.
I think the aCLI maintainers have been improving this by reacting quicker to these kind of issues, but maybe we could set up something that installs the CLI on a VM every day, and alerts if it doesn’t work?
They felt overwhelmed by all the different components (aUI, aAPI, aCLI, aOS…) and would have preferred to just see a “simple” mode, and then have more advanced documentation as needed.
We should also make the initial docs better, so the architecture feels easier to understand.
With getting into frameworks, developers give up some flexibility in exchange for some benefits.
We need to be more clear and direct on the tradeoffs, maybe a documentation page about it would be great.
Permission system feels complex
We should expand on the tradeoffs of the permission system, since that’s the most important thing we ask developers to buy into.
It takes forever to run the first time
They cited installing dependencies as the main bottleneck.
aragonUI is easy and enjoyable
They highlighted that aragonUI felt minimal and easy to adapt without hacks, which is good to hear!