I actually really like Remix 3’s event pattern - in fact, it was literally what we explored with React Flare like 5 years ago whilst on the React team with @necolas. If you can build event subsystems that compose as self contained logic with their state then it simplifies things a lot. We didn’t ship React Flare because of many reasons - not related to the credits of the idea. I still think there’s a valid place for them though. Personally I didn’t find any of the other Remix 3’s experiments that impressive. They’ve all been done before in some capacity and found to have pitfalls. I admit though that every pattern or idea has pitfalls, but that’s my vibe. A good example is the DOM diffing on Frame, how does that work with dynamic components and lists? The whole getting the developer to do update() isn’t new either, Bobril and Ivi did that 5 years ago. I congratulate new ideas and shared reasoning though. I noticed `context.get/set’ API in there - just like Ripple, which was validating. One question @ryanflorence, how do you spread events through composite components in this pattern? Do you expect people to pluck “on” and re-spread it?

Complete rewrite is usually code for “I don’t understand anything in this codebase so maybe if I do it myself I will?”

don’t be a sheep