←back to thread

The GitHub website is slow on Safari

(github.com)
446 points talboren | 1 comments | 27 Aug 25 09:43 UTC | HN request time: 0.307s | source
Show context
adithyassekhar ◴[27 Aug 25 14:51 UTC] No.45040524[source]▶
This thread has really opened my eyes to how much the world hates react developers, I am one.

Unrealistic timelines, implementing what should be backend logic in frontend, there's a bunch of ways SPA's tend to be a trap. Was react a bad idea? Can anyone point to a single well made react app?

replies(13): >>45040699 #>>45040711 #>>45040798 #>>45040947 #>>45041164 #>>45041374 #>>45041377 #>>45041379 #>>45041735 #>>45043250 #>>45043659 #>>45047956 #>>45050341 #
bapak ◴[27 Aug 25 19:04 UTC] No.45043659[source]▶
After having worked on React for a while, I can tell you that the problem remains between monitor and chair.

React can have all the niceties and optimization in the world, but that fails when its users insist on using it incorrectly, building huge tangled messy components and then wondering why a click takes 1.3 seconds to deliver feedback.

replies(2): >>45046506 #>>45049396 #
1. mvdtnz ◴[28 Aug 25 07:20 UTC] No.45049396[source]▶
The problem that is that react doesn't have a pit of success. Because it's poorly conceived, poorly designed and poorly written software made by people more interested in getting the word "homomorphism" onto their CV than solving real problems. You knew when they started using terms like "monad" and "functor" in order to attach a click handler to a button that something had gone badly wrong.

In this very thread there's some asshole using the word "memoization" when "caching" would have been fine.