3 ms·

There's a not-entirely-small part of me that hopes Issues breaks entirely for long enough that people at GitHub rethink their implementation. GH issues have be

by japhyr 2y ago

There's a not-entirely-small part of me that hopes Issues breaks entirely for long enough that people at GitHub rethink their implementation. GH issues have been so useful for the better part of a decade, that I have an empty repo called my_life just so I can make issues about things like home maintenance. In the last few months, the UI has become so slow and flaky that I don't use it for nearly as much as I used to. And when I have to for a project, it slows me down noticeably. I thought I was alone in this, but asking around I found that this is a common frustration among developers I communicate regularly with.

RohMin 2y ago
That's actually a really interesting way to leverage that feature. Have you found this easier than other services built specifically for this use case?
- japhyr 2y ago
  I've tried other tools. But I'm on GitHub most days, so it's been a seamless way to keep track of some things that would otherwise disappear into a calendar, or some tool that I don't use as often.
jrochkind1 2y ago
I am not experiencing a full outage right now, but I am experiencing very slow (spinner) and flakey (error that works again on repeat). So perhaps it's the same problem, that's been getting more prevalent until it was noticeable by monitoring. One can hope!
deleted 2y ago
[deleted]
simonw 2y ago
I do the same - I've been running so many non-software things out of private GitHub Issues. I even have a simple system for creating a new issue every day to use as a personal TODO list, described here: https://til.simonwillison.net/github-actions/daily-planner https://til.simonwillison.net/github-actions/daily-planner I've noticed everything feeling a whole lot less snappy and responsive over the past few days - ironically I think it's because they've done a major rewrite of the frontend presumably with the aim of making it more snappy and responsive!
straws 2y ago
You're not alone. There's been an effort to transparently update the UI to a React implementation over the past year or two, and while I understand the benefits to that approach, they have introduced some flakiness in moving away from a the server-rendered pjax/html-pipeline/simple web components approach that was so cohesive and battle tested over the decade before it.
PapaPalpatine 2y ago
I’m low-key certain it’s because they started using more React on the front end, especially for the new Issue stuff. The entire UI feels slow and janky like GitLab.
joseda-hg 2y ago
For something so critical, does it make sense to self host say a gitea instance or such? I know you can sync repos, I don't think you can sync issues tho
- snapplebobapple 2y ago
  this is what i doits worth the 11 dollars a year for the vps to control my own

by japhyr 2y ago

RohMin 2y ago

That's actually a really interesting way to leverage that feature. Have you found this easier than other services built specifically for this use case?

japhyr 2y ago
I've tried other tools. But I'm on GitHub most days, so it's been a seamless way to keep track of some things that would otherwise disappear into a calendar, or some tool that I don't use as often.

jrochkind1 2y ago

I am not experiencing a full outage right now, but I am experiencing very slow (spinner) and flakey (error that works again on repeat). So perhaps it's the same problem, that's been getting more prevalent until it was noticeable by monitoring. One can hope!

deleted 2y ago

[deleted]

simonw 2y ago

I do the same - I've been running so many non-software things out of private GitHub Issues. I even have a simple system for creating a new issue every day to use as a personal TODO list, described here: https://til.simonwillison.net/github-actions/daily-planner https://til.simonwillison.net/github-actions/daily-planner I've noticed everything feeling a whole lot less snappy and responsive over the past few days - ironically I think it's because they've done a major rewrite of the frontend presumably with the aim of making it more snappy and responsive!

straws 2y ago

You're not alone. There's been an effort to transparently update the UI to a React implementation over the past year or two, and while I understand the benefits to that approach, they have introduced some flakiness in moving away from a the server-rendered pjax/html-pipeline/simple web components approach that was so cohesive and battle tested over the decade before it.

PapaPalpatine 2y ago

I’m low-key certain it’s because they started using more React on the front end, especially for the new Issue stuff. The entire UI feels slow and janky like GitLab.

joseda-hg 2y ago

For something so critical, does it make sense to self host say a gitea instance or such? I know you can sync repos, I don't think you can sync issues tho

snapplebobapple 2y ago
this is what i doits worth the 11 dollars a year for the vps to control my own