Class Components Vs. Functional Components in React.js

Dec 8, 2020·

2 min read

When I embarked on my React journey, I initially delved into the realm of functional components. As I attempted to decipher the intricacies of the code, I watched and read numerous tutorials and occasionally sought assistance on StackOverflow, albeit not dedicating as much time as I should have. Nevertheless, this quest led me to stumble upon components with a distinct syntax that differed from the familiar functional components I had grown accustomed to. These peculiar entities, as it turned out, were known as class components.

Allow me to present a brief snippet of each component type for a clearer comparison:

functional component:

const Animal = () => {
    const name = 'Ruffus';
    return (
        <p>My dog's name is {name}!</p>

class component:

class Animal extends React.Component {
    constructor() {
      this.state = {
        name: 'Ruffus'
    render() {
      return (
        <p>My dog's name is {}!</p>

Numerous instances left me feeling disheartened when I couldn't complete certain projects due to my struggle to comprehend the process of transforming class components into functional counterparts. So, besides the obvious syntax variance, what truly distinguishes these two component types?

In short: not much.

To elaborate further: Functional components have always been an integral part of React, but prior to version 16.8, they lacked the capability to handle state. Consequently, developers had to resort to class components when dealing with state management. However, with the advent of version 16.8, React introduced Hooks, granting functional components the ability to retain state. This pivotal addition eliminated the necessity of exclusively relying on class components.

In summary, both functional and class components yield identical results. The choice between the two ultimately rests upon your personal preference and requirements.