4 ms·

the gh cli tool If your site is so awful that you're forced to use the command line to navigate it, something is quite wrong. You're seriously suggesting that

the gh cli tool If your site is so awful that you're forced to use the command line to navigate it, something is quite wrong. You're seriously suggesting that it's an acceptable workflow to go from your browser to the command line just to preserve infinite scrolling? There's already an issue search feature on Github, why shouldn't that be improved to return relevant search results? My solution was to dial back my engagement with github (e.g. using a project's gitweb) and move to a different platform for hosting my own stuff. Also, Lazy loading is pagination. No, it's not. Infinite scrolling means you're loading all of the content instead of a page at a time.

bastardoperator 3y ago
You think GitHub is just a website at this point? LOL. I do a lot of work in the terminal so I for one welcome a tool that enables productivity without having to visit a website. I know, it's a crazy concept, like wow. When I use the search feature for text in the hidden comments, it brings me to that issue. As a pointed out below, you're also wrong and you can easily see that the comments are not loaded, are paginated, and that the loading of more comments only happens when you click the link to display more. The fact that it only displays 60 comments at a time and wont load any additional comments unless you click for more is why it's not infinite scrolling because after 60 comments, you're at the bottom of the page, unless you click, not scroll, for more.
- inferiorhuman 3y ago
  You think GitHub is just a website at this point? I never said that. I do a lot of work in the terminal so I for one The cheese stands alone. You're (deliberately?) missing the point. There's nothing inherently wrong with a command line workflow. What's wrong is breaking a workflow (e.g. browser) and then suggesting it's appropriate to simply fall back to the command line for part of that. As a pointed out below, you're also wrong Well, no. You're focused on the API (which nobody commenting here cares about one whit) and not the interface. While the comments may be loaded in batches they're not paginated within the browser. Look, you prefer the command line and that's great for you. That preference doesn't justify gimping the site.

bastardoperator 3y ago

You think GitHub is just a website at this point? LOL. I do a lot of work in the terminal so I for one welcome a tool that enables productivity without having to visit a website. I know, it's a crazy concept, like wow. When I use the search feature for text in the hidden comments, it brings me to that issue. As a pointed out below, you're also wrong and you can easily see that the comments are not loaded, are paginated, and that the loading of more comments only happens when you click the link to display more. The fact that it only displays 60 comments at a time and wont load any additional comments unless you click for more is why it's not infinite scrolling because after 60 comments, you're at the bottom of the page, unless you click, not scroll, for more.

inferiorhuman 3y ago
You think GitHub is just a website at this point? I never said that. I do a lot of work in the terminal so I for one The cheese stands alone. You're (deliberately?) missing the point. There's nothing inherently wrong with a command line workflow. What's wrong is breaking a workflow (e.g. browser) and then suggesting it's appropriate to simply fall back to the command line for part of that. As a pointed out below, you're also wrong Well, no. You're focused on the API (which nobody commenting here cares about one whit) and not the interface. While the comments may be loaded in batches they're not paginated within the browser. Look, you prefer the command line and that's great for you. That preference doesn't justify gimping the site.