Way overcomplicating design is one challenge that keeps getting worse.

Another gigantic unspoken issue is that people have started building tons of stuff with React on purpose for some reason.

▲

MatthiasPortzel 9 hours ago | parent | next [-]

React gets blamed for this because the error handling is bad and the UX is confusing. But the issue with GitHub’s frontend is that the backend is dropping requests. When you click a button on GitHub and the loader gets stuck that’s because there no timeout/error handling in the JavaScript but there also no reply from the server. I feel like React is getting a bad rap because it’s visible when the issue is clearly their backend.

	▲	regularfry 7 hours ago \| parent [-]
		> React gets blamed for this because the error handling is bad and the UX is confusing Yes, it does. > React is getting a bad rap because it’s visible when the issue is clearly their backend. Two things can be bad! Except that in this case one of them is unnecessarily bad, because nobody forced them to use a front end system which defaults to terrible failure handling.

▲

pc86 9 hours ago | parent | prev [-]

This is surprising to me, I would have bet money that all the people who actively engage in this type of language/framework war discourse were all drawing Social Security by now.

	▲	12_throw_away 9 hours ago \| parent [-]
		There's a big difference between a war between two somewhat equivalent things that make different choices (editor wars, language wars, etc.) vs pointing out that certain things are really fundamentally ... not good. IMO we all need to be much louder and clearer about how bad things are, and how much better they could be. This is, in fact, on topic: github actions seemed to me like a bad idea from the start, to me, but I let my co-workers and "network effects" convince me that I was being grumpy and that it was fine, and so we've adopted it. And now ... here we are. It was exactly as bad I thought it was, and it reflected a broken engineering culture.