5 Cliches About React Js You Should Avoid
With the growth in the adoption and popularity of React Js, there are also several cliches about React Js. Think of these cliches as myths and misconceptions that often pop up during a discussion about the tool.
Initially, React Js was a Facebook thing, but it has grown to become the main tool of AirBnB, Instagram, PayPal, and many other tech giants.
On GitHub, React has close to 160k stars, while the core library has grown to about 9 million weekly downloads.
With the unprecedented growth React Js has enjoyed since its initial release in 2013, it has also bred its share of misconceptions, myths, and cliches. In this article, we’ll address 5 of the cliches about React Js.
1. React Promotes Inline Styles
This is nothing but a dogmatization to think that there’s no diverse way of handling styling in React Js. If you’ve worked on different applications and projects, you’ll rarely see people using inline style with React.
Usually, people start any React project with create-react-app, and there are three options out of the box; CSS, SCSS, and css-modules.
You’ve got to be able to decide by yourself what approach suits your project the best.
2. React Does Not Use Web Standards
This is one cliché about React Js you’ll find too funny to even argue for or against.
While the term “web standard” has been used arbitrarily, you should know these people refer to CSS, HTML, and JS. Don’t forget that React relies on JS, and ReactDom Reconciler converts it into HTML loads. In the end, the browser requests for CSS if there’s a need for it at the beginning.
This abides by all attributes of web standards.
3. The Inaccessible Nature of React
The origin of this cliché is from developers who are uninterested in writing accessible applications. This is not just a React Js thing as it exists across all development frameworks. It’s a general thing rather than being just a React Js thing.
What makes it a React thing is the wide adoption of the library. A lot of efforts have to be invested into training developers within the ecosystem on developing accessible applications.
So, avoid contributing to this cliché about React.
4. React Has a Long Learning Curve
When you are aiming to learn every concept within the React API, then you may be right.
However, anything outside of this will be a cliché. While many have happened to the React ecosystem with the way code is written, it has not taken away the old way of writing codes.
There’s quite a lot of possibility around React. You can choose to write in React using just the class while you also have the option of working with functions; the choice is yours.
5. To Use React, JSX is Required
The popularity of JSX is brought about by React as a way of defining the UI of an application.
While the syntax shares semblance with HTML, it is backed by JavaScript’s power, making it understand what a specific component renders. This cliché about React is why some people are not using the library since they believe it negates the principle of separation of concerns.
JSX is never a requirement to use React. You can even choose to use a template language.
Final Thoughts
To avoid the cliches about React Js, you’ve got to approach every technology with the respect it deserves.
The idea behind this article is to shed light on the truth about React Js. With a view on highlighting what React Js brings to the table and why you should consider it for your next project.