Live data from Hacker News

Making our new homepage fast and performant

github.blog

91–100 of 144 posts

Re: Making our new homepage fast and performant

#91

I don't understand the fad in making content flop around the page as one scrolls. At the very least, it would be courteous of them to respect the prefers-reduced-motion media query. https://developer.mozilla.org/en-US/docs/Web/CSS/@media/pref...

> prefers-reduced-motion media query

Thanks for this. (Yet) another fingerprinting vector I didn't know about.

Re: Making our new homepage fast and performant

#93

I don't understand the fad in making content flop around the page as one scrolls. At the very least, it would be courteous of them to respect the prefers-reduced-motion media query. https://developer.mozilla.org/en-US/docs/Web/CSS/@media/pref...

The worst part is that those animations get replayed when scanning back over earlier parts of the page.

Re: Making our new homepage fast and performant

#96
post #18

What does the word performant mean exactly?

Based on their examples:

* Consistent UI performance under load. Not the same as "goes faster", just "doesn't slow down".

* More efficient resource/CPU utilization.

* Smarter loading of resources (kind of a sub point of 1)

I think they're trying to say it's "consistently not-slow and efficient with resources". Does "fast" express that well? To grandma, sure. To a technical audience, no.

https://dictionary.cambridge.org/us/dictionary/english/perfo...

Re: Making our new homepage fast and performant

#98

i hate the new circular avatars. A few weeks ago, github avatars were square and it looked much better. It is also contrary to the published github visual guidelines. EDIT: quote from the current github style guide: Avatars are images that users can set as their profile picture. On GitHub, they're always going to be rounded squares. They can be custom photos, uploaded by users, or generated as Identicons as a placeho…

Frankly, I hate the trend of rounding everything, and have a few rules in my user stylesheet to square things up again everywhere.

Re: Making our new homepage fast and performant

#99
OT but "performant" is not a word. I know what your[0] saying: "but everyone uses it alot[1]". Irregardless[2] if I just mis-use[3] characters frequently enough, am I suddenly right?

[0] incorrect word/grammar. [1] also not a word. [2] actually a word but don't use it. [3] not correct.

Re: Making our new homepage fast and performant

#100
post #79

You know what pages I'd like to be fast and performant on github? The PR discussion and diff page. When a PR gets really large (thousands of LOCs and hundreds of comments) (yes I know it's bad to do that, that doesn't help me a lot when it happens), despite them hiding everything so you need dozens of clicks in order to be able to actually read and search through it's slow as hell and it's a mess. This is not helped…

I have hit the final crater you mentioned so often, I now manually visit the url /myorg/myrepo/compare/old-master...my-new-feature to start the PR instead of clicking "Create PR" or "Compare"

I use the hub[0] cli tool to manually specify the branch when I create a PR.

[0]: https://hub.github.com/hub-pull-request.1.html

Post reply on HN