Adam Solove
Jul 25, 2017 · 1 min read

This is a fantastic and very relevant question. For me personally, it took a few weeks of free time and funemployment to empty my brain of immediate concerns and step back to think about the larger issues in my recent work.

If we want to talk about generic adoption, I think the curve might look something like React:

  • The first time you hear about it, it violates all your expectations (“XML and inline events?”, “documentation instead of working code?”) and you reject it
  • The second time you hear about it, you have a problem that it might solve (“remembering how/when to change the DOM is hard”, “understanding what should happen in all cases is hard”), but it still seems to crazy.
  • Later, as more people start sharing stories about their successes with the new idea, they also help to work out a better way to explain the concept to newcomers and evangelize its benefits.

I think we’re still at step 1 for understandable behavior, but making some progress. I know an upcoming conference talk in the React world will include discussion of modeling behavior via state machines. And I know of a few other people using the technique in real work, so I think we’ll be hearing more soon.

    Adam Solove

    Written by

    Building web UIs. Everything should be faster.