Explore the 'Why should you use statecharts?' and 'Why should you not use statecharts?' sections on statecharts.dev. List at least three benefits and two downsides of using statecharts as presented on the website. Additionally, identify if there are any links on the homepage or in the footer that point to external resources like libraries, tools, or a community forum (other than the previously attempted GitHub discussions).
Navigate to 'https://statecharts.dev/'. Scroll down to the 'Why should you use statecharts?' section. Identify and list at least three benefits of using statecharts. Scroll down to the 'Why should you not use statecharts?' section. Identify and list at least two downsides of using statecharts. Thoroughly examine the entire homepage, including the footer, for any links to external resources, libraries, tools, or community forums (excluding the GitHub discussions that were previously attempted and failed). Report any found external links or state that none were found.
At least three benefits of using statecharts are listed (e.g., easier to understand, behaviour decoupled, easier to make changes, easier to reason about code, tested independently, all states explored, lower bug counts, deals with exceptional situations, scales well, great communicator). At least two downsides of using statecharts are listed (e.g., programmers need to learn something new, foreign way of coding, team pushback). The agent clearly states whether any external links to libraries, tools, or community forums were found on the homepage or in the footer, providing the URLs if found, or stating that none were found.