The key feature of ReactJS :
It's library and not a framework:
ReactJS is a component-based javascript library which is used for building an interactive and dynamic user interface. A Framework gives you more features for a greater cost. But despite its great features, the cost of React is relatively small.
Anything that is not about rendering a view is not a Reacts responsibility. Despite the fact that many React apps are built in conjunction with Redux, nobody forces developers to do so. It's just a convenient way to build data flows in an app. Even if you want to render some part of an application using other tools, React is okay with that.
Components:
Components let you split the UI into independent, reusable pieces, and think about each piece in isolation. That’s why components written by different people will work well together. Components just need to get data to show as props. Where do you find it? None of their business.
Declarative:
The way a developer describes a components view in React is declarative. You declare how a component should look with every possible set of props. In the declarative paradigm you describe what program should do, not how to do it.
Performance and Virtual DOM:
The main ReactJS Feature is the Virtual-DOM where only one-way data binding is present. Virtual DOM adds advantages where it compares the new data with original DOM and automatically updates the view. It's a one-way data binding hence manipulating the virtual DOM is quick rather than updating original DOM because nothing gets drawn onscreen.
Debugging:
When something goes wrong, it is important that you have breadcrumbs to trace the mistake to its source in the codebase. In React, props and state are those breadcrumbs.
React has a community of millions of developers and users:
———————————————————————
Source and credits:
Thanks!
It's library and not a framework:
ReactJS is a component-based javascript library which is used for building an interactive and dynamic user interface. A Framework gives you more features for a greater cost. But despite its great features, the cost of React is relatively small.
Anything that is not about rendering a view is not a Reacts responsibility. Despite the fact that many React apps are built in conjunction with Redux, nobody forces developers to do so. It's just a convenient way to build data flows in an app. Even if you want to render some part of an application using other tools, React is okay with that.
Components:
Components let you split the UI into independent, reusable pieces, and think about each piece in isolation. That’s why components written by different people will work well together. Components just need to get data to show as props. Where do you find it? None of their business.
Declarative:
The way a developer describes a components view in React is declarative. You declare how a component should look with every possible set of props. In the declarative paradigm you describe what program should do, not how to do it.
Performance and Virtual DOM:
The main ReactJS Feature is the Virtual-DOM where only one-way data binding is present. Virtual DOM adds advantages where it compares the new data with original DOM and automatically updates the view. It's a one-way data binding hence manipulating the virtual DOM is quick rather than updating original DOM because nothing gets drawn onscreen.
Debugging:
When something goes wrong, it is important that you have breadcrumbs to trace the mistake to its source in the codebase. In React, props and state are those breadcrumbs.
- If you see something wrong on the screen, you can open React DevTools, find the component responsible for rendering, and then see if the props and state are correct. If they are, you know that the problem is in the component’s render() function, or some function that is called by render(). The problem is isolated.
- If the state is wrong, you know that the problem is caused by one of the setState() calls in this file. This, too, is relatively simple to locate and fix because usually there are only a few setState() calls in a single file.
- If the props are wrong, you can traverse the tree up in the inspector, looking for the component that first “poisoned the well” by passing bad props down.
React has a community of millions of developers and users:
———————————————————————
Source and credits:
Thanks!
Post a Comment