davidkpiano

5 ms·

1. 1.▲
   by davidkpiano 2mo ago

   Author here; still in alpha!
2. 2.▲
   by davidkpiano 4mo ago

   Pretty cool. Looks like stately.ai but catered towards agentic state machine workflows. Really interesting!
3. 3.▲
   by davidkpiano 5mo ago

   This would be the closest: https://github.com/GnomesOfZurich/scxml/
4. 4.▲
   by davidkpiano 5mo ago

   I loved this talk!
5. 5.▲
   by davidkpiano 5mo ago

   P lang is close: https://github.com/p-org/P
6. 6.▲
   by davidkpiano 5mo ago

   There is also @xstate/store for simple event-driven stores and atoms; just as simple as Zustand + Jotai: https://stately.ai/docs/xstate-store
7. 7.▲
   by davidkpiano 5mo ago

   The next version of XState will be much more ergonomic, with a reduced API surface area, lower learning curve, and much easier for devs (and agents) to author. But at the same time, frontier models are very good at writing XState.
8. 8.▲
   by davidkpiano 5mo ago

   Statecharts are still getting some traction! XState has over 4 million weekly npm downloads. Animation tools like Rive & LottieFiles heavily advertise state machine capabilities. AI tools like LangGraph are built on state machine founda
9. 9.▲
   by davidkpiano 5mo ago

   Glad to see statecharts still getting attention! I created XState, a JS/TS library for authoring, executing, and visualizing state machines/statecharts: https://github.com/statelyai/xstate I've been work
10. 10.▲
    by davidkpiano 7mo ago

    Really appreciate you using XState!
11. 11.▲
    by davidkpiano 7mo ago

    Really cool! Love the XState-inspired API ;-)
12. 12.▲
    by davidkpiano 1y ago

    Re: atoms + learning curve, this is why XState Store exists, which supports both XState-style state updates and atoms: https://stately.ai/docs/xstate-store I also like the approach of Svelte, and realize that sometimes
13. 13.▲
    by davidkpiano 2y ago

    Thank you for the kind words! I somewhat agree that it is complicated and overly engineered for many applications that don't need all of the statechart features, and that it has a sizable learning curve. I plan on greatly simplifying i
14. 14.▲
    by davidkpiano 2y ago

    I remember this! It was one of my inspirations for creating a hierarchical state machine editor [0] and a state machine library with a visualization layer [1]. [0] https://state.new [1] https://github.com/stately
15. 15.▲
    by davidkpiano 2y ago

    Hey thanks for linking, I'm still working on this and hope to have a beta release soon! Stately Agent is a completely open-source library for creating (LLM) agents that adhere to state machines.
16. 16.▲
    by davidkpiano 2y ago

    How does this compare to the state machine editor on https://state.new ?
17. 17.▲
    by davidkpiano 3y ago

    There are a lot of resources on finite state machines, especially in TypeScript, here: https://stately.ai/docs/state-machines-and-statecharts
18. 18.▲
    by davidkpiano 3y ago

    (Creator here) Thank you for the mention!
19. 19.▲
    by davidkpiano 3y ago

    Oh hey it's me!
20. 20.▲
    by davidkpiano 3y ago

    You don't need to define every possible state. A state machine can serve as a higher-level structure of some of the states (statuses, modes) of parts of your app, for ease of structuring logic. But you can also create a single-state st
21. 21.▲
    by davidkpiano 3y ago

    XState creator here! I love that use-case. We have plenty of developers & companies using XState on the backend, and one of our main goals for XState v5 was to enable more backend use-cases, with custom & composable actor logic, dee
22. 22.▲
    by davidkpiano 3y ago

    This looks awesome!
23. 23.▲
    by davidkpiano 3y ago

    Thanks for sharing! There's an updated viz at https://stately.ai/viz but that will soon be fully part of the studio at https://state.new (which can export to Mermaid now and PlantUML soon!)
24. 24.▲
    by davidkpiano 3y ago

    Congrats on the launch, this looks really interesting!
25. 25.▲
    by davidkpiano 3y ago

    Would love to know more about an example "simple embedding use-case" that you may have in mind. We're not trying to force state machines as the solution for any state-related problem; they're not a panacea, but instead a
26. 26.▲
    by davidkpiano 3y ago

    Yes! Visualizing how different actors communicate with each other in general is a big goal for us this year. We're going to start with sequence diagrams.
27. 27.▲
    by davidkpiano 3y ago

    Hey, creator of XState here! Just want to mention that we're very close to releasing XState v5 beta, which brings even more features to the state machines & statecharts you can create, and greatly improves the developer experience,
28. 28.▲
    by davidkpiano 4y ago

    Hey, XState creator here. What did you not like about XState? Hopefully there are areas we can improve on or questions we can answer. Or maybe it wasn't appropriate for the project?
29. 29.▲
    by davidkpiano 4y ago

    Creator of XState here - I agree. State machines and statecharts should be used to model parts of your application that need it, and they can potentially communicate with each other. Fitting the entire app in a single state machine is just
30. 30.▲
    by davidkpiano 4y ago

    Yep, the "stateless" part of the state machine is its transition function.