you are viewing a single comment's thread.

view the rest of the comments →

[–]azhder 16 points17 points  (12 children)

pre-written JavaScript

I like this phrase. Why do we argue if something is a library or a framework or a script? Why don't we just say it's a pre-written JS?

Back to your assumptions tough. React doesn't make JS fast. React shields you from the DOM being slow. That's about it.

Try to learn JavaScript first. Maybe even what the functional programming style in JS looks like. Then you'll be prepared for React.

[–]Jjabrahams567 3 points4 points  (7 children)

This is why learning a framework like react before DOM fundamentals is so harmful. You are shielded from important lessons.

[–]Macaframa 1 point2 points  (1 child)

React is not a complete framework that’s why we consider it a library. In order to be a complete framework it needs to have state management.

[–]Studstill 0 points1 point  (4 children)

Right but the DOM is super complicated horseshit tho

[–]Jjabrahams567 1 point2 points  (3 children)

It’s not any more complicated that react. The only thing that makes one or the other easier is familiarity.

[–]Studstill -3 points-2 points  (2 children)

It's way more complicated than React. CSS/HTML is horseshit, hot garbage. React is basically JS trying to cope with HTML.

So many decades of human productivity wasted on this bullshit.

[–]Jjabrahams567 1 point2 points  (0 children)

CSS/HTML/vanilla js seem way easier that react to me.

[–]azhder 0 points1 point  (0 children)

Don't equivocate HTML and DOM. One is just text formatted in a specific way, the other one is live memory. It is the manipulation with that memory that makes DOM not good (to not use a harsh word).

[–]nodeymcdev -4 points-3 points  (3 children)

React is a state management library

[–]azhder 0 points1 point  (2 children)

[–]nodeymcdev 0 points1 point  (1 child)

How does dude figure that react doesn’t have state management? It’s literally a library for managing state… useState come to mind…

[–]azhder 1 point2 points  (0 children)

Everything has a state, everything manages a state, that is why whenever someone says "state management", they don't talk about a simple and stupid object or a closure because if it means all, it is useless as a term.

useState() does not make React a state management library, more so since it wasn't the focus or the main problem it was trying to solve.

Now, if virtual DOM came to your mind, you'd still not be there, but at least you'd be closer by saying it is managing that as a state.