Despite the fact I like some of the changes presented there, one particular detail has shot me: lack of understanding why github has put commit messages in file list and removing it - this might be a harsh opinion, but proved to me that the author doesn't fully understand how most users (developers) are using GitHub.
Redesigning GitHub Repository Page
251–260 of 315 posts
Re: Redesigning GitHub Repository Page
#252This is so Microsoft redesigns the Github repos https://www.youtube.com/watch?v=EUXnJraKM3k
Re: Redesigning GitHub Repository Page
#253[deleted]
Re: Redesigning GitHub Repository Page
#254Following his decisions along, they make sense, but the final product is convoluted and busier than the original.
Re: Redesigning GitHub Repository Page
#255Earlier quoted context omitted.
No, it's not nostalgia, goddammit. It's because it contains good visual affordances. Skeumorphism isn't pretty, but it works because our eyes are naturally trained to perceive the visual hints. Our eyes are trained to subconsciously perceive depth via shadows. To perceive clear edges and group things by them. I really, really hate that 99% of all UX designers are basically graphic designers who are good with visual f…
>I really, really hate that 99% of all UX designers are basically graphic designers who are good with visual flourish but without the tiniest bit of interest into half a century worth of HCI research into what makes interfaces visually easy to read You probably won't be downvoted because of the audience bias here, but that's like saying "I really hate that 99% of all engineers are basically code monkeys with zero und…
I have a master in interaction design and I'm being critical of my own field.
EDIT: Also, no, I did not misunderstand what skeuomorphism is, your own definition of it is what is too limited. Using fake depth and shadows on a design element to give it a 3D look like a real-world button is a form of skeuomorphism, because it relies on an understanding of real-world buttons that can be pushed.
Re: Redesigning GitHub Repository Page
#256Earlier quoted context omitted.
However, a lions share of the revenue for github will be from developers, rather than "consumers".
The point was that developers themselves are often browsing repositories they do not own/contribute to.
And what is it those developers are doing?
Personally, I'm reading the README and/or looking at the contents of files. Plus looking at issues. Very rarely am I looking for the releases tab.
I'm amused that people are using the "I only do this every 6 months so I can't remember where it is" argument. If you only need the functionality every 6 months, perhaps not having it in your face every time you use it might be a good thing ...
Re: Redesigning GitHub Repository Page
#257Earlier quoted context omitted.
>I really, really hate that 99% of all UX designers are basically graphic designers who are good with visual flourish but without the tiniest bit of interest into half a century worth of HCI research into what makes interfaces visually easy to read You probably won't be downvoted because of the audience bias here, but that's like saying "I really hate that 99% of all engineers are basically code monkeys with zero und…
Even if he is wrong about the literal meaning of skeumorphism- he very well pointed out what was right about the windows UI. And I think his intension with the charged statement was to convey the meaning that people talk without knowing what they are talking about.
My intention with discussing the meaning of skeuomorphism is to also convey that people talk without knowing what they are talking about.
Being vaguely angry about "young designers" and their "hip flat interfaces" is a common trigger on HN. I've seen it here countless times, and its rarely insightful. The argument is rooted in a the fallacy that designers only care about making "pretty" things.
Likewise, I've also heard it the same way towards engineers. 99% of engineers only care about cool technical solutions and not meeting users needs. When you've drawn such a broad stroke, it's not a basis for good discussion...just a flamewar.
Re: Redesigning GitHub Repository Page
#258Earlier quoted context omitted.
Even if he is wrong about the literal meaning of skeumorphism- he very well pointed out what was right about the windows UI. And I think his intension with the charged statement was to convey the meaning that people talk without knowing what they are talking about.
My intention with discussing the meaning of skeuomorphism is to also convey that people talk without knowing what they are talking about. Being vaguely angry about "young designers" and their "hip flat interfaces" is a common trigger on HN. I've seen it here countless times, and its rarely insightful. The argument is rooted in a the fallacy that designers only care about making "pretty" things. Likewise, I've also he…
I think he only got the name wrong- he was right about what caused Win UI to "just work" and in general about how the shadow stuff is useful
Re: Redesigning GitHub Repository Page
#259Earlier quoted context omitted.
Even if he is wrong about the literal meaning of skeumorphism- he very well pointed out what was right about the windows UI. And I think his intension with the charged statement was to convey the meaning that people talk without knowing what they are talking about.
My intention with discussing the meaning of skeuomorphism is to also convey that people talk without knowing what they are talking about. Being vaguely angry about "young designers" and their "hip flat interfaces" is a common trigger on HN. I've seen it here countless times, and its rarely insightful. The argument is rooted in a the fallacy that designers only care about making "pretty" things. Likewise, I've also he…
> Being vaguely angry about "young designers" and their "hip flat interfaces" is a common trigger on HN.
No, the triggering part of your message was the "nostalgia" claim, which isn't supported by the evidence. Even young people typically have an easier time finding their way around interfaces with an older visual design than a modern flat design (all else being equal). This has been tested.
The fact that you claimed it anyway tells me that you have opinions on UI design but don't bother to check if they hold up.
Re: Redesigning GitHub Repository Page
#260> 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…
> 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.