concerns in websites.
"React abstracts away the DOM from you, giving a simpler
programming model and better performance. React can also
render on the server using Node, and it can power native apps
using React Native."
What`s inside React.js
- Complexity to compare two trees is O(n^3) complexity
- React.js managed to turn O(n^3) problem into linear O(n)
- So it`s really fast
"This coupling is real, and it is unavoidable. We must bind event
listeners to elements on the page. We must update elements on
bidirectionally and in real-time with the elements of the DOM.
... the mantra of React is to stop pretending the DOM and the
— Keith J Grant
You can fake and control states of your html component
combining CSS declarations and JS conditions.
Everything is global.
Selectors are matched against everything in the DOM.
CSS grows over time.
People are afraid of their own CSS. You can't just delete
things as it's so hard to know if it's absolutely safe to do
You can be more dynamic with styles in a programming
You can make really cool stuff with sass, but its not really
The scary "global" nature of CSS is neutered. A module
over here is styled like this, a module over there is styled
like that - probably no conﬂicts in sight.
One sense I get is that some people just like and prefer
style to change based on dynamic conditions (states) on
What do you get out of inlining styles?
Colin Megill - Inline Styles are About to Kill CSS
Some people really like this idea!
You can ﬁnd people in the world who like
eating excrement, it doesn't mean it's a
Styling is what CSS is for
This is the "religious" angle that probably isn't
going to take us very far.
The separation of concerns is inherent to CSS.
It`s a ﬁle just for styling.
Inline styles are at the top of the speciﬁcity
The !important declaration can still win a speciﬁc
property/value styling war over an inline style, but
that's a slightly different concept and an even grosser
war to ﬁght.