They were, and still very much are, using web components. But they hired a team to do experiments to imagine the future of GitHub UI, and that team built everything in React. Now that team's work is being ported to the production UI.

▲

mdhb 5 days ago | parent | next [-]

Also as a part of their bullshit React rewrite in addition to making everything much much slower they also managed to break basic functionality like the back and forth buttons on Safari that only got fixed quite recently but for a good 9-12 month period it was impossible to use on iOS.

Genuinely whoever was a part of pushing this rewrite should have been fired.

	▲	jdlshore 4 days ago \| parent [-]
		I know you’re just expressing your frustration, but the “the person who did this should be fired” meme you’re propagating is pretty toxic. Decisions like this are never the work of one person, and even when they are, any problems you’re perceiving were traded off against other problems you’re not perceiving. And even if it was an unadulterated mistake, it’s just that… a mistake. Should you get fired for the mistakes you make? I guess what I’m really saying is that the internet would be a better place if you and others like you dialed down the rhetoric, dialed down the outrage, and dialed up the empathy. Thanks for listening.

▲

koakuma-chan 5 days ago | parent | prev | next [-]

Just use that thing that renders React 1000x faster, million JS or something

	▲	Dlanv 5 days ago \| parent [-]
		it has some limitations: https://old.million.dev/docs/manual-mode/block#breaking-rule... and it isn't a silver bullet on its own

▲

5 days ago | parent | prev [-]

[deleted]