What? React has nothing to do with current state of affairs. In fact, React on GitHub currently exists in mere islands, i.e. in Projects and recently in Pull Requests. Most of the frontend is still Web Components[1] paired with Turbo[2] for hot reloading. GitHub is still as slow even with JavaScript disabled, try it yourself. Backend just serves stuff really slow. In fact, there is an alternative GitHub frontend (no affiliation) that feels snappier and is written in React.[3]

With that said, Mitchell complains about outages. These started directly after Microsoft acquisition[4] and are attributed to migration from AWS to Azure.

[1] https://github.blog/engineering/architecture-optimization/ho...

[2] see html source for tags

[3] https://my.githero.app/

[4] https://damrnelson.github.io/github-historical-uptime/

▲

jrochkind1 9 hours ago | parent [-]

Pull Requests is the thing that was wacky in the UI yesterday, coincidence or not? I have no idea.

Yesterday we saw PR pages that displayed no error, just displayed wrong info. I would have preferred to get an error page than outdated or empty lists. I was guessing this was related to the React migration but I don't really know.

	▲	hylaride 7 hours ago \| parent \| next [-]
		Also, the browser back and forward buttons no longer work in pull requests when going between PR tabs (commits, checks, files changed, etc) as well as some other site interactions. Like, what user-hostile intention was the reasoning behind that? I am literally imagining a product manager smoking a cigar and laughing at the RUM session replays of me losing my shit.
	▲	queenkjuul 8 hours ago \| parent \| prev [-]
		I think the backend is just fucked. I have issues with Actions and the API all the time, not just the web UI