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.
Making our new homepage fast and performant
101–110 of 144 posts
Re: Making our new homepage fast and performant
#102This is neat, in a look-what-i-can-do sort of way. And I do appreciate the write-up. However.... (and there's always a but) does this page convert better? And if it doesn't, will they have the guts to rollback? I don't know anything about the politics behind github and the employees. I'm sure they're all wonderful people. This is just a projection from my company. Even if the new flashy design performed 20% worse, it…
I think this question is just as much about data as it is intuitive and feelings. Does a rollback make the front page of HN? Does the newer version leave a lasting impression that can't be measured? I don't think you can truly measure these things without actually measuring sentiment, etc. I'm sure Netflix has seen increased metrics across the board but everything they've done and added in the last three years or so…
Re: Making our new homepage fast and performant
#103"Making GitHub's least visited page fast and performant"
Re: Making our new homepage fast and performant
#104Amazing hack with the SVG mask and embedded JPEG to compensate for web browsers not supporting WebP images! This trick was used to get an image that has both transparency and lossy compression. I would have loved to see the face of the engineer who thought of this hack, tried it, and saw that it worked for the first time. :)
Re: Making our new homepage fast and performant
#105Re: Making our new homepage fast and performant
#106Safari has become the new IE in a lot of ways as far as compatibility. A good first step would be to stop gating Safari updates behind OSX updates.
Re: Making our new homepage fast and performant
#107You 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…
Is there anything novel here? GitHub is nowhere close to a delight as people make it out to be. Settling for GitHub creates as many problems as it solves. This is not a recent development, and there's nothing surprising about any of this (at least it shouldn't be considered surprising at this point). What's interesting that if you ask people why they love GitHub, they'll probably say, "because of its community and it…
Re: Making our new homepage fast and performant
#108Earlier quoted context omitted.
It's one of the few truly bad design paradigms made popular by Apple in recent years. Their site has always been full of it.
>made popular by Apple in recent years. Oh I have vivid memories. Mac Pro Trashcan 2013. If I remember correctly it was the first time Apple turns to using lots of animations for their product page. Before that Apple's product page were fast, beautiful and elegant. The TrashCan webpage was using lots of animations to show case their cant innovate anymore my ass . Your MacBook Fan would spin up simply by scrolling thr…
I also remember that for the longest time ever they had a far too clever trick to show movie-quality videos at a time when browsers didn't really have video. They would have dozens of png pictures that they would stitch and change on the fly using Javascript. And it worked surprisingly well.
Re: Making our new homepage fast and performant
#109Who goes to GitHub's home page? I have 27 repositories on GitHub and I'd never been to their home page until today.
Re: Making our new homepage fast and performant
#110Earlier quoted context omitted.
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
https://marketplace.visualstudio.com/items?itemName=GitHub.v...