What is the difference between functional components with hooks and class components?

What is the difference between functional components with hooks and class components?

• A. Functional components with hooks can be stateful and use lifecycle-like features; class components use this.state and lifecycle methods; modern React favors functional components.
• B. Class components are the only way to use state.
• C. Functional components cannot have state.
• D. There is no difference.

Answer: (A)

Functional components with hooks gain state and lifecycle-like behavior, while class components rely on this.state and explicit lifecycle methods. Hooks like useState let a functional component hold and update state, and useEffect lets it run code at mount, update, and unmount times, effectively giving you lifecycle capabilities without a class. This combination makes functional components as capable as class components for managing state and side effects, but in a simpler, more modular function-based style. Modern React favors this pattern because it’s easier to read, test, and reuse through custom hooks, while keeping components smaller and more focused. The idea that class components are the only way to use state is outdated. The claim that functional components cannot have state is simply incorrect thanks to useState. And saying there’s no difference ignores the concrete differences in syntax and lifecycle handling, as well as the modern approach that centers functional components with hooks.

Functional components with hooks gain state and lifecycle-like behavior, while class components rely on this.state and explicit lifecycle methods. Hooks like useState let a functional component hold and update state, and useEffect lets it run code at mount, update, and unmount times, effectively giving you lifecycle capabilities without a class. This combination makes functional components as capable as class components for managing state and side effects, but in a simpler, more modular function-based style. Modern React favors this pattern because it’s easier to read, test, and reuse through custom hooks, while keeping components smaller and more focused.

The idea that class components are the only way to use state is outdated. The claim that functional components cannot have state is simply incorrect thanks to useState. And saying there’s no difference ignores the concrete differences in syntax and lifecycle handling, as well as the modern approach that centers functional components with hooks.