davidkpiano

9 ms·

1. 61.▲
   by davidkpiano 6y ago

   Completely agree with you, and thanks for the kind words about XState! (I'm the creator)
2. 62.▲
   by davidkpiano 6y ago

   I'll experiment with this.
3. 63.▲
   by davidkpiano 7y ago

   Oh wow, I barely remember writing this 4+ years ago! I still hold to it - specificity is a necessary mechanism, and if it's hard, it's because we're unnecessarily over-complicating it, just like anything else considered &quot
4. 64.▲
   by davidkpiano 7y ago

   I made a visual cheat-sheet here: https://excalidraw.com/#json=5149387806212096,XD-zzKj7vlSIgw...
5. 65.▲
   by davidkpiano 7y ago

   This is the paper (by David Harel) that initially inspired me to create XState a few years ago. Here is a direct PDF link: http://www.inf.ed.ac.uk/teaching/courses/seoc/2005_2006/reso... Many of the idea
6. 66.▲
   by davidkpiano 7y ago

   If you have enough discipline, sure. Finite state machine tools like XState are more strict about this.
7. 67.▲
   by davidkpiano 7y ago

   It's not exactly the same. Statecharts have more "features" than just hierarchical states: - Parallel (orthogonal) states - History (shallow, deep) states - Entry, exit, transition actions - Delays - "Throughout" ac
8. 68.▲
   by davidkpiano 7y ago

   That's awesome to hear! (Author of XState here) For those curious: XState is a JavaScript state machine/statechart library that doesn't invent any new concepts and instead adheres strictly to statechart principles and the SCX
9. 69.▲
   by davidkpiano 8y ago

   Working on this with XState! Let's talk.
10. 70.▲
    by davidkpiano 8y ago

    Really awesome to hear! I strongly agree with the notion that all popular front-end frameworks have an API that encourages tying business logic with UIs, and this is has been a known anti-pattern for decades now.
11. 71.▲
    The FaceTime Bug and the Dangers of Implicit State Machines(medium.com)

    4 points by davidkpiano 8y ago|0 comments
12. 72.▲
    by davidkpiano 8y ago

    > They don't get stuck in spaghetti code This is quite the assumption! Bottom-up text-based programming leads to much greater complexity because most programmers don't properly model their software (e.g., with state machines, s
13. 73.▲
    by davidkpiano 8y ago

    Both.
14. 74.▲
    by davidkpiano 8y ago

    Thank you, I appreciate it!
15. 75.▲
    by davidkpiano 8y ago

    You can fork the pen and implement them. Have fun!
16. 76.▲
    by davidkpiano 8y ago

    Sorry for coming off as ignorant/condescending, it was definitely not my intention. But to be fair, I asked this question a year ago and the majority of front-end developers were unfamiliar with state machines: https://twitt
17. 77.▲
    by davidkpiano 8y ago

    Make a PR ;-) I have limited time to work on the docs but will be working to improve accessibility this week. Also, how's this for a nicer tone? "It would be great if this site supported better keyboard navigation, like using the
18. 78.▲
    by davidkpiano 8y ago

    I appreciate the thanks :) I'm currently into React, but in a very light way -- I'm going to continue experimenting with how statecharts can (semi-)universally define the behavior of complex components in a way that can be integra
19. 79.▲
    by davidkpiano 8y ago

    IMO, state machines are becoming a "big deal" because front-end developers are finally realizing that there is a name (and strict formalism) for the patterns that they've been using to manage complex UI behavior. Not only is
20. 80.▲
    by davidkpiano 8y ago

    I'm actually working on such a tool! I'll have a beta out in early 2019. For now, you can use this visualizer: https://statecharts.github.io/xstate-viz
21. 81.▲
    by davidkpiano 8y ago

    Thank you - this is correct (the interpreter is impure). It also makes it possible to create your own custom interpreters. Also, your work has been a huge influence on XState, and I can't thank you enough for SCION!
22. 82.▲
    by davidkpiano 8y ago

    Hey! I made XState and just discovered it hit Hacker News (...great) To clarify, the new tag-line is "State machines and statecharts for the modern web." Some of you are nitpicking the word "stateless" which describes th
23. 83.▲
    by davidkpiano 8y ago

    Hey @midhunsezhi, I'm the creator of xstate and am working on the next version (very few, if any, breaking changes) which includes adding documentation on one of the most important use cases of statecharts - as a refactor target. Would
24. 84.▲
    by davidkpiano 8y ago

    Thanks so much for the praise (I created `xstate`)! I'm working hard on making it fully SCXML-compatible.
25. 85.▲
    by davidkpiano 9y ago

    Thanks! I have some awesome updates to announce very soon!
26. 86.▲
    by davidkpiano 9y ago

    Hey! I'm the creator of xstate: https://github.com/davidkpiano/xstate - a pure, functional, declarative implementation of statecharts in TypeScript. It has zero dependencies, is frameworkless, and fast (O(n) state
27. 87.▲
    by davidkpiano 9y ago

    A surprising number of developers (especially in the web/native app dev world) are unfamiliar with state machines, especially in regard to UI development. The idea of "when an event occurs, the state changes" might be a natur
28. 88.▲
    by davidkpiano 9y ago

    Another similar article: https://css-tricks.com/robust-react-user-interfaces-with-fin... (full disclosure, I wrote this) There is definitely a learning curve to state machines, and even more so with statecharts/UML. It
29. 89.▲
    Show HN: Nm8, a tiny JavaScript animation lib under 260 bytes(npmjs.com)

    3 points by davidkpiano 9y ago|0 comments
30. 90.▲
    by davidkpiano 9y ago

    I think the big misconception here is that statecharts _have_ to be framework-y. They don't, and their biggest benefit (in my opinion) is how they shift the mental model of creating UIs from "bottom-up" to "top-down&quot