Phỏng vấn 20'

anonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·tech

anonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·tech

anonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·tech

anonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·tech

anonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·tech

anonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·tech

anonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·tech

anonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·tech

anonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·tech

anonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·techanonymous · 23:44 3/6/26 · ORA·tech

Pitfall re-render của Context API trong React Native là gì và cách khắc phục? · ORA·tech

Trung bình Pro#react-native

Pitfall re-render của Context API trong React Native là gì và cách khắc phục?

15 tháng 2, 2026

Tóm tắt nhanh

Pitfall lớn nhất của Context API là không có cơ chế tự động so sánh nông (shallow comparison); khi giá trị `value` của Provider thay đổi reference, mọi component tiêu thụ (consumer) đều bị buộc phải re-render, dù chúng chỉ sử dụng một phần dữ liệu không hề thay đổi. Trong React Native, điều này gây sụt giảm hiệu năng nghiêm trọng (drop FPS) do luồng render của JS liên tục gửi lệnh cập nhật qua Bridge/JSI tới Native UI.

guest · ORA·techguest · ORA·techguest · ORA·techguest · ORA·techguest · ORA·tech

guest · ORA·techguest · ORA·techguest · ORA·techguest · ORA·techguest · ORA·tech

guest · ORA·techguest · ORA·techguest · ORA·techguest · ORA·techguest · ORA·tech

guest · ORA·techguest · ORA·techguest · ORA·techguest · ORA·techguest · ORA·tech

guest · ORA·techguest · ORA·techguest · ORA·techguest · ORA·techguest · ORA·tech

guest · ORA·techguest · ORA·techguest · ORA·techguest · ORA·techguest · ORA·tech

Nội dung dành cho Pro

Mở khoá toàn bộ câu hỏi Trung bình & Nâng cao + đáp án chi tiết.

Nâng cấp Pro

Câu hỏi liên quan

Trung bình Pro

Trung bình Pro

Trung bình Pro

Trung bình Pro

Phân biệt `StyleSheet.create` và inline style trong React Native: Khi nào nên dùng?

Quay lại chủ đề