Congratulations on building apple.com
Making our new homepage fast and performant
121–130 of 144 posts
Re: Making our new homepage fast and performant
#122Earlier quoted context omitted.
It really hasn't. Most of the shiny new features that Chrome pushes are actively objected by both Mozilla and Webkit teams.
Yeah, but there are a growing number of areas where Chrome and Firefox have nearly identical behavior and Safari is the odd one out. Text overflow ellipsis inheritence handling and sticky elements in a scrolling flex container off the top of my head. But there seems to be lots of those things where it works fine in FF and Chrome but not Safari. Further, Apple seems to show little interest in improving. About what you…
We can pick and chose whatever area we decide to view identical or diverging. The fact of the matter is this: https://web-confluence.appspot.com/#!/confluence
- Chrome: 7602 web APIs
- Firefox: 6572 web APIs
- Safari: 6335 web APIs
(Web APIs include everything, including CSS, see API catalog at the top right of the page).
If anything, Firefox is identical to Safari. This is especially evident if you look at the "browser-specific" tag
Safari is adding 150 to 400 new APIs with each release. It's harder to see this because their cadence has historically been tied to new OS releases (so, yearly, and really wish they'd increase the cadence). Meanwhile, in the latest version alone Chrome released 75 new APIs. And they release 20 to 70 new APIs in every version which they release monthly [1].
Yes, Safari may be less prioritized than other teams at Apple, but in no conceivable way, shape, or form are they "the new IE6".
Re: Making our new homepage fast and performant
#123Cool, 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 why even simple static-content websites are so fucked up nowadays? Where does it come from? Who does it benefit? What drives this madness?
Re: Making our new homepage fast and performant
#124You 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…
[deleted]
Re: Making our new homepage fast and performant
#125Earlier quoted context omitted.
Yeah, but there are a growing number of areas where Chrome and Firefox have nearly identical behavior and Safari is the odd one out. Text overflow ellipsis inheritence handling and sticky elements in a scrolling flex container off the top of my head. But there seems to be lots of those things where it works fine in FF and Chrome but not Safari. Further, Apple seems to show little interest in improving. About what you…
We can pick and chose whatever area we decide to view identical or diverging. The fact of the matter is this: https://web-confluence.appspot.com/#!/confluence - Chrome: 7602 web APIs - Firefox: 6572 web APIs - Safari: 6335 web APIs (Web APIs include everything, including CSS, see API catalog at the top right of the page). If anything, Firefox is identical to Safari. This is especially evident if you look at the "brow…
I agree "the new IE6" is a tad much, but this...
> there are a growing number of areas where Chrome and Firefox have nearly identical behavior and Safari is the odd one out.
...is definitely true for me when developing relatively simple sites. I develop in Firefox and it's been a long time since I've had to change any CSS to make it work in Chrome. Meanwhile Safari has had broken default SVG sizing for years now (unless they fixed it recently), ignores padding on (so you need to set the height) and other things like that.
It's all minor, but it's annoying to deal with. Especially considering you need Apple hardware to test with.
But I can't complain too much, since I also still need to support IE11.
Re: Making our new homepage fast and performant
#126Who goes to GitHub's home page? I have 27 repositories on GitHub and I'd never been to their home page until today.
It's like a big university sign in front of campus. I never took photo with it from first to last day. It's for outsiders!
Re: Making our new homepage fast and performant
#127Earlier quoted context omitted.
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.
To be fair, I go look at Stripe's homepage every couple months just because it's pretty.
I do this too :)
Re: Making our new homepage fast and performant
#128Cool, 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…
Too many people with a lot of time and not enough more useful things to do. I guess it benefits the believers of resume-driven-development.
Re: Making our new homepage fast and performant
#129Earlier quoted context omitted.
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
For me, I hit Command+Shift+P in VS Code, choose Open pull request, then hit Enter. As easy as it gets. https://marketplace.visualstudio.com/items?itemName=GitHub.v...
...or have even more PR functionality with https://marketplace.visualstudio.com/items?itemName=CodeStre...
Re: Making our new homepage fast and performant
#130OT 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.