3 ms·
> http://tonsky.me/blog/github-redesign/60_icons-removed.png http://tonsky.me/blog/github-redesign/60_icons-removed.png Why should a user without any backgroun
by lqet 8y ago
> http://tonsky.me/blog/github-redesign/60_icons-removed.png http://tonsky.me/blog/github-redesign/60_icons-removed.png
Why should a user without any background in coding / git, care about the branches when opening an issue? Or individual commits? Not the mention that the number of commits may change depending on the selected branch, but the issues and releases stay the same, which is something the author does not talk about.
> If you are a programmer, you might be surprised but other people normally don’t like hierarchies.
Citation needed.
One of the big benefits of a hierarchy (be it in UI design or on a political / social / corporate level) is that on any level, you really don't have to think about the levels above or next to you that much, and thus even individuals with a very limited skill set can be productive members of this hierarchy. The anarchic approach of "everything is accessible to anyone everywhere" taken here just excludes specialists from using a GUI productively.
- oblio 8y ago> Citation needed. All the popular modern interfaces don't use trees, they use lists and lists of lists. Technically those are trees, but not to users, since they're only exposed to 1 level at a time. And regarding the "anarchy" is solved another way: searching and sorting, à la Knuth. The most successful interface of all time, Google, has 1 input and 1 button and it returns a list of things.