[tqkxzugoaupvwqr]

Yet performance is abysmal. I clicked on “API reference” and nothing happened for a second. Then the submenu opened in the sidebar. Another second later the content view updated. There is no indication of anything loading, there are no network requests to await. Incredibly, it’s dog slow on an M1 Mac.

If the viewport is 800 px or narrower, click on the menu icon (horizontal bars, top right), then click on a sidebar link. Do that a few times, you’ll notice it’s incredibly slow to react. Same with resizing the viewport, very sluggish.

[FridgeSeal]

Good lord it’s awful haha.

Some more unhinged stuff I noticed:

- swiping backwards exists the drop down menu for some inexplicable reason

- clicks on menu bar items take so long I genuinely thought I hadn’t tapped on it correctly.

- taps on the menu bar sometimes just don’t work. Like, at all. Oh scratch that, the menu was there after I swapped tabs to write this sentence.

- massive chunks load in at different times: the signing key page shifts as more content loads in 3.5 seconds later.

[phist_mcgee]

There's something to be said for optimistic routing, server or client side. It seems like they're using suspense to wait for the page to be rendered before swapping the route. It's a noticeable breach of the standard pattern of instant navigation, and then wait for content to appear.

[FridgeSeal]

I really wish it was possible for users browsers to opt-out of stuff like this. I don’t want some unhinged developer deciding they’d like to arbitrarily delay things like this, just render the page and stop making things worse.

[treis]

Wow you weren't kidding. Very slow and very frustrating to use.