From 54920ee88af03ce71db3257e726edfe2cc5e8aab Mon Sep 17 00:00:00 2001 From: Segun Adebayo Date: Wed, 27 Apr 2022 10:06:36 +0400 Subject: [PATCH] chore: update readme --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index fc544cbf8e..7e387976a3 100644 --- a/README.md +++ b/README.md @@ -16,9 +16,9 @@ Finite state machines for accessible JavaScript components With the rise of design systems and component-driven development, there's an endless re-implementation of common component patterns (Tabs, Menu, Modal, etc.) in multiple frameworks. -Most of these implementations seem to be fairly similar in spirit, the only difference is that they use framework -specific idioms (like `useEffect` in React.js). They tend to grow in complexity over time and often become hard to -understand, debug, improve or test. +Most of these implementations seem to be fairly similar in spirit, the differences being around the reactivity and +effects systems for the framework (e.g. `useState`, `useEffect` in React.js). Framework specific solutions tend to grow +in complexity over time and often become hard to understand, debug, improve or test. ## Solution