Ancestors

Written by Eric Matthes on 2025-01-22 at 14:29

I think GitHub issues reloads the page every time you check a task now. 🤦‍♂️

I used to love GH issues, and I have issue trackers for all aspects of my life, such as home maintenance tasks. It's becoming unusably slow. :/

=> More informations about this toot | More toots from ehmatthes@fosstodon.org

Toot

Written by Eric Matthes on 2025-01-22 at 14:38

Here's what checking a couple tasks at the bottom of a longer task list looks like for me, on Safari:

=> View attached media

=> More informations about this toot | More toots from ehmatthes@fosstodon.org

Descendants

Written by Bill Mill on 2025-01-22 at 15:12

@ehmatthes I created an issue with 100 checkboxes, and clicked the 100th. What I see in the inspector is a >500ms graphql query; it seems rather than optimistically update the UI, they disable it until the server acknowledges the write

=> View attached media

=> More informations about this toot | More toots from llimllib@hachyderm.io

Written by Eric Matthes on 2025-01-22 at 15:18

@llimllib It's frustrating to see this because GH has been so thoughtful about some aspects of their work, such as building an effective search engine for codebases and repositories.

Last year I would check things, and refresh the page only to find that the checks weren't persisting. That needed to be addressed, but "reload the entire page after every check" doesn't seem like a good approach?

=> More informations about this toot | More toots from ehmatthes@fosstodon.org

Written by Bill Mill on 2025-01-22 at 15:28

@ehmatthes yeah, I just checked what linear does, and it's the sensible approach to me: let the user update the page as much as they like and notify the server every time, and persist the result

I wonder if github now renders issue markdown in ways that can only be accomplished on the server, making it difficult to allow the optimistic update of the UI and preventing them from having a responsive experience

=> More informations about this toot | More toots from llimllib@hachyderm.io

Written by Eric Matthes on 2025-01-22 at 15:41

@llimllib Usability should be one of the highest priorities. It should kick off some actions that can be only taken on the server, but the UI in 2025 can be made responsive. Or it could refresh, and retain the scroll point.

My guess would be that the framework they're using to implement the UI doesn't make either of these easy, so they haven't bothered to make it meaningfully responsive.

It's clearly a work in progress, so I hope they do address it.

=> More informations about this toot | More toots from ehmatthes@fosstodon.org

Written by Bill Mill on 2025-01-22 at 16:24

@ehmatthes I started a discussion here: https://github.com/orgs/community/discussions/149748

It's unlikely to result in anything, but maybe it will at least motivate a ticket to get filed

=> More informations about this toot | More toots from llimllib@hachyderm.io

Written by Eric Matthes on 2025-01-22 at 16:29

@llimllib Thanks for filing that, I upvoted and shared that clip as well.

=> More informations about this toot | More toots from ehmatthes@fosstodon.org

Written by Dan Sloan on 2025-01-22 at 15:42

@ehmatthes I’m impressed, that’s actually “good”. I can’t even get it to load in safari anymore, it immediately locks up. I had to switch to Firefox just to be able to do anything.

=> More informations about this toot | More toots from LucidDan@fosstodon.org