Every browser gives me a different result, I guess I can't blame the site for that. But it should perhaps mention which browser would be the most accurate.
They've published a series of articles on this project:
>So this is how a lot of our assets ended up being primarily designed in real life as painted paper-cutout models. The models are then photographed, taken apart and scanned. Some paint samples are also created specifically to become tileable.
I find it insane that everybody is seemingly okay with the fact that websites get to know what a user was browsing before landing on their site. And that there's no straightforward way to disable this behavior without the use of extensions.
I've been a split ergo keyboard user for many years now. Seen a lot of people decide to go from a traditional keyboard to a split ergo keyboard only to end up hating it.
This is too big of a jump to make in one go, and the sudden overhead in the amount of new information your mind and fingers need to get adjusted to ends up overwhelming a lot of people.
When you switch to a custom keyboard like the one you did. It's not just a split keyboard you're switching to, you also move to a smaller form factor that has lesser keys, and an ortholinear layout which has column stagger instead of row stagger. It's most effective to transition by gradually moving to the next form factor only after you're fully comfortable with the previous ones.
In your case, something like the Kinesis freestyle would have been a much better choice for you.
I've seen tons of very active projects under Google's GitHub org[1] that have the disclaimer "This is not an officially supported Google product" so I would take a guess that they have a much better policy on employees participating in OSS than Apple does.