Hacker News Reader

Try it on a flaky connection. Every menu (maybe any action of any kind?) makes a roundtrip to the server before displaying, with a very slow timeout. It's crazy how bad it is.

View on HN

Not just that, some actions spawn an entire Chromium instance. For example, any time you click on a music video (not a new thread, an actual full Chromium instance).

I’m sure more agentic coding loops will improve these inefficiencies

Are you joking? Inefficiencies like that are a typical tell for LLM-generated slop.

And I'm sure their prompt whisperers are proud of their work.

Yes I was joking

I think they've gotten worse about this as an organization over the last few years(?). Earlier this year an update to their mobile app introduced loading time, and resulting slowness, for opening menus that used to be ~instant. To me that smacks of once having known not to do that, but that knowledge having been lost (or priorities having shifted).

More specifically, I'm talking about tapping the '...' on a track for the options menu. That should be latency-free, and used to be.

That specific thing hasn't been latency free for me for years.

Though I agree it should be.

Reply on news.ycombinator.com