องค์ประกอบไร้สถานะเทียบกับมีสถานะ

Welcome to this lesson on UI components! As you build digital products, you'll encounter two main types of components: stateless and stateful.

Understanding their differences is key to building efficient, maintainable, and reusable user interfaces.

First, let's briefly define what a UI component is. Think of it as a self-contained, reusable piece of a user interface.

• Buttons, input fields, navigation bars, and cards are all examples of UI components.
• They encapsulate their own logic and appearance.
• They make building complex UIs much more manageable.

Stateless components are like pure functions: given the same inputs, they will always produce the same output.

• They don't store or manage any internal data that changes over time.
• They receive data (often called props) from their parent component.
• They are predictable, simple, and primarily concerned with displaying information.

Here's a simple example. This WelcomeMessage component just takes a name and displays it. It doesn't remember anything or change itself.

Stateless components offer several advantages:

• Simplicity: Easier to understand, debug, and test.
• Predictability: Their output is always the same for the same input.
• Reusability: Can be used in many different places without side effects.
• Performance: Often render faster as they have less internal logic.

Stateful components, on the other hand, can manage and change their own internal data, called state. This state influences how they look and behave over time.

• They react to user interactions or other events.
• Their output can change even with the same initial inputs.
• They introduce dynamic behavior to your UI.

This Counter component keeps track of a number and can increment it. Its render output changes based on its internal count state.

Deciding between stateless and stateful components is a common design choice:

• Stateless: Ideal for displaying static content, presentational elements, or when data is entirely managed by a parent. Think buttons, icons, or simple text blocks.
• Stateful: Necessary when a component needs to respond to user input, manage form data, fetch external data, or maintain any changing internal value. Think input fields, toggles, or interactive dashboards.

While stateful components are powerful, they add complexity. Aim for stateless components whenever possible to keep your UI predictable and easier to manage.

• Maintainability: Stateless components are easier to test and reason about.
• Debugging: Tracing issues in stateless components is simpler.
• Performance: Minimizing stateful components can lead to better performance by reducing complex re-rendering logic.

Which of the following characteristics are TRUE for stateless components? Select all that apply.

You've learned the fundamental differences between stateless and stateful components!

• Stateless: Purely presentational, receives props, no internal state, predictable, highly reusable.
• Stateful: Manages internal state, dynamic behavior, reacts to interactions, more complex.

Choosing the right type helps build robust and efficient design systems.