- Joined
- Jun 19, 2024
HTML is not only easier to code, shit like React is a solution to problems that don't exist. Its dogshit, I gave up on trying to get better at react because quite frankly, I dont want to code react even if somebody was paying me to do it. I'm gonna code vanilla html and I'm not installing any bullshit libraries unless I actually find them useful. Express and bootstrap for example, are pretty good.
Why do you guys shit on React so much when you don't even know why it exists, and why it's bad?im more so talking about the language used, ist very 2019 leftward shift redditesque.
what i will say is i thought react was just supposed to make websites look nicer? like i understand you can create a competent website using html but if you want the bells and whistles you use react no?
React exists precisely because "just use HTML" falls apart beyond a certain scale ("scale" in the sense of quantity of pages/interactions) of UI where you need to update things (preferably without making the user sit through a reload.) This really goes back to AJAX, which enabled websites to be enormously more efficient. When you got your response from an AJAX call, you needed to update what the user was seeing to reflect the result of the request. When you just need to do that once or twice, it's no big deal, but if you have a website as big as Facebook, managing these updates gets really messy. This is where a framework comes in: A tree of DOM subtrees have their intended appearance declaratively specified such that the logic for updating them to reflect changes can be completely automated. That's enormously valuable for an organization like Facebook.
Now we get to the "why it's bad" part. React was created by "Functional Programming" jackoffs who tried to force a stateless paradigm onto an inherently stateful system, and React has become a convoluted nightmare over the years as the tensions between the stateful DOM and stateless React have required more and more convoluted workarounds. As for why it's so often React, it's basically just because it was first (Angular as initially released is basically dead; a lot of users left for other frameworks between major versions.)
Now, you might be saying "Wait a minute, AJAX is more efficient than loading the entire website any time the user does anything, but modern websites using frameworks are enormous, what gives?" And to that, I say: Jeets. Frameworks encapsulate components well enough that, for the most part, you really don't need to worry about how the sausage is made, and most of those sausage makers are just focused on making their particular component look right, and usually have a poor understanding of what's going on under the covers, so a lot of really clunky and bloated stuff makes it into the ecosystem.
Now, why is every retard using React, or some other framework, for websites that don't really need it? Consider:
- Businesses have a strong tendency to prematurely scale. (For example, businesses with 50 users using Kubernetes with dynamic scaling.)
- If you're a web developer, every website you make is resume fodder, and saying you "made a site in React" helps you get employed, "I made a small, clean HTML website" doesn't.
- Unfortunately, lots of "coding bootcamps" and the like teach React like it it's own programming language, and users don't even know how to write JS normally.
tl;dr use Svelte
ETA: Some of you guys do this with LISP too, but in the other direction. People seem to assume that the only reason we aren't all using LISP is because we're all just not enlightened enough, and the s-expression syntax normiefiltered the masses too hard. I don't know exactly why LISP failed, but it has real problems that can be considered instead of just "too much parens
Last edited: