I liked the old home page better.
Making our new homepage fast and performant
131–140 of 144 posts
Re: Making our new homepage fast and performant
#132OT 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.
This is funny and deserves more upvotes. :D
Regrettably, this unfortunate usage of "performant" is common in our field (and on HN) and is already infecting dictionaries.
In this example it seems to be used as computing jargon for "good according to some (unspecified) performance criteria."
Google's (Oxford Languages) dictionary gives a similar definition:
(COMPUTING) adjective: performant: functioning well or as expected. "a highly performant database which is easy to use"
This would seem to be a very poor and unclear substitute for words like "fast" or "efficient" or "reliable" or even "effective."
Re: Making our new homepage fast and performant
#133OT 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.
Language is evolution.
[deleted]
Re: Making our new homepage fast and performant
#134OT 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.
Language is evolution.
Language evolution isn't always good.
Re: Making our new homepage fast and performant
#135OT 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.
I googled "performant" but the search result wasn't performant. https://www.google.com/search?&q=performant
Haha, indeed.
The google incantation (yielding its definition as a computing jargon term for "functioning as expected") seems to be "performant definition" but "performant" is still a terrible word.
Re: Making our new homepage fast and performant
#136The consensus on HN seems that of a page has more than 20 lines of JS it's trash and bloated.
Normal people don't see the web the same way HN does. Normal people like pretty things, and people like creating pretty things. Designers wanted to creat a pretty webapge, and I found said webpage pretty. Not to mention that the website loads pretty quickly, so all those complaints about performance are incredibly hollow. If someone is working with 2g internet they have bigger issues than trying to visit Github's homepage.
Re: Making our new homepage fast and performant
#137Cool, but why go through all this trouble? A simple website would do the same job. I really don't understand where this constant urge for things like crazy animations comes from. Just built a simple website that provides the content users are looking for. You can make it look good an professional without much code. You won't need to make a blog post to explain how you made it perform well. Can someone explain to me w…
Humans love creating art. We have always wanted to make things look pretty.
Re: Making our new homepage fast and performant
#138Talking about nice looking homepages that load fast the first one that came to mind is Stripe's. It starts with 952.83 KB / 364 KB transferred and goes to 1.70 MB / 482.03 KB transferred on final load (once you reach the bottom of the page) Github's starts with 3.10 MB / 969.27 KB transferred and goes to 6.64 MB / 4.54 MB transferred Yeah, Github's homepage has more content, it's true... but what I find really amazin…
Wow. It's been a while I hadn't a look at the Stripe homepage. This is raising the bar. How does one go about drawing those nice device mockups with code? I assume it's a combination of svgs and canvas, but probably built using specific software?
Re: Making our new homepage fast and performant
#139The fastest way to make it fast and performant is moving these 'Webgl' animations to a separate page like 'Github Globe'. Leave only text,
no fancy effect, nothing irrelevant to 99% of users.
Re: Making our new homepage fast and performant
#140Earlier quoted context omitted.
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…
Fair enough, but is there a viable alternative? Continuing withe the OP's main complaint: Gitlab's PR review is also slow and not even for a 1000 LOCs, feels even slower to me than Github actually.
Of course there is. There's Gitlab and Gitea, at the very least. They aren't very popular, but they don't need to be as long as signing up is easy or as long as they offer federated/social login.