"How to make a webpage fast and performant",
- Starts to explain how to use the most obscure javascript functions
- Explains how to show a real time , websocket animated globe of users of github
Lol
Making our new homepage fast and performant
51–60 of 144 posts
Re: Making our new homepage fast and performant
#52This JPGs-in-a-SVG thing is grotesque, an example of how web development often seems like a Jenga tower of hacks. Why not find minimally-perceptible pixel changes to the image that allow it to compress better as PNG?
PNG is lossless while JPG is lossy so I'm not sure how you'd want to do this.
Re: Making our new homepage fast and performant
#53A way to make GitHub's new homepage strictly faster is by removing the dynamic bits
Re: Making our new homepage fast and performant
#54You wouldn't have had to spend so many hours on making the page fast if you had just cut down on some of the fluff and focused on the content instead.
Re: Making our new homepage fast and performant
#55[deleted]
Re: Making our new homepage fast and performant
#56i 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…
I use to feel the same way, but I've been slowly incorporating the circular avatars into my own solution. I don't know why GitHub changed things, but from my own personal experience, I've found circular avatars to be "less distracting".
I'm guessing by cropping more of the image, my attention doesn't focus on them as long. If I want the focus to last longer, I'll still use rectangular avatars since they contain more information. See example below to see how I mix-match things.
Re: Making our new homepage fast and performant
#57how about making the PR experience less garbage on keeping track of comments across changesets
Re: Making our new homepage fast and performant
#58What does the word performant mean exactly?
It usually means something like "fast enough" or "faster than expected". In this title "fast and performant" is using redundancy for emphasis.
Re: Making our new homepage fast and performant
#59I 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...
I find them quite annoying. I'm pretty sure the only people enjoying these kind of animations are the designers themselves. Most people don't go to a website to have an "experience". They just want to find some information as fast and easily as possible.
> Most people don't go to a website to have an "experience".
Well, with the things that people do routinely, they rarely do it for the experience. But that does not mean they do not experience it. That experience should certainly be prioritized while keeping the goal of the users as a top priority.
Re: Making our new homepage fast and performant
#60Earlier quoted context omitted.
I think it means fast, but it's used when someone wants a buzzword. I wish people would use fast instead. I feel the same way with learnings (use lessons ).
The title is “Making GitHub’s new homepage fast and performant” which suggests performant is something different from (just) fast.
Just a guess: maybe it means fast-despite-fancy-junk. So, it contrasts with just fast achieved by keeping the content simpler and less fancy?