Follow

@Rana That plays a part in managing the complexity, but that doesn't entirely escape it. I think it is essential to create a mentality in the team of reducing complexity as much as possible. That means reusing metaphors, avoiding "nice to haves" when possible, providing good APIs so people can customize, etc. A great example is how has stuck with a two-level namespace (e.g. github.com/one/two) even as it has become massive. 's subgroups are an example of bad design IMHO

Sign in to participate in the conversation
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml