Re:New React DevTools
by chrisco255 on Friday August 16, 2019 @03:04AM
(#20712807)
All of these things work with React, too. React appropriately names the prop to "dangerouslySetInnerHtml" because it's vulnerable to XSS attacts and a lot of beginner web developers don't realize that.
CSS has of course always worked just fine with React (as does LESS and SASS). Styled-components is totally optional.
There's tradeoffs at scale with trying to use an imperative style of coding with document.querySelector or JQuery. Fine for simple websites. Absolutely awful for complex web apps with large teams.
Dom explorer is still a tab in Chrome for react devs. I readily switch between the React devtools and Dom explorer all the time.
The reason in my mind, for React, is that it's a higher level, functional abstraction above the DOM that makes complex web development manageable.
CSS has of course always worked just fine with React (as does LESS and SASS). Styled-components is totally optional.
There's tradeoffs at scale with trying to use an imperative style of coding with document.querySelector or JQuery. Fine for simple websites. Absolutely awful for complex web apps with large teams.
Dom explorer is still a tab in Chrome for react devs. I readily switch between the React devtools and Dom explorer all the time.
The reason in my mind, for React, is that it's a higher level, functional abstraction above the DOM that makes complex web development manageable.