What's coming next & Superfine v. Hyperapp

Here is a mixed list of current and upcoming Superfine features and changes. Some of these may not be available to Hyperapp or vice-versa. I’m planning to work through these after Hyperapp V2 is out.

• Typescript rewrite.
  • Use more ES6 features, e.g., Map, arrow functions, destructuring.
• Superfine will continue to support lifecycle events as a pragmatic solution for enter/exit animations, encapsulation of state, global event listeners, etc. See https://github.com/hyperapp/hyperapp/issues/717 for more uses and why they’re going to be removed from Hyperapp.
• Lazy views. See: https://github.com/hyperapp/hyperapp/issues/721
  • Lazy views allows you to declare a part of your VDOM should be re-rendered only when some data changes. This features is equivalent to Elm’s Html.lazy.
• Expose eventProxy.
  • Intercepting DOM events allows Hyperapp to couple VDOM and state management. Another use could be auto-redrawing. What else could you use it for?
• JSX fragments (vnodes of type array) #71.
• Explore class components (not available to Hyperapp)
• Shadow DOM?

---

[jorgebucaran]

@132yse You’re probably looking at Hyperapp 1’s VDOM, hence the confusion.

Superfine (this project) and Hyperapp 2’s VDOM code is essentially the same, therefore performance is the same too.

Hyperapp 2 doesn’t include lifecycle events (Superfine still does) and DOM events dispatch actions directly, making it faster than Superfine, but possibly not for a lot.

Or did Hyperapp lose some of its performance for size?

No, it didn’t.

[jorgebucaran]

Superfine 7 is out. I think we’re done here. Some of the stuff I wrote up there is either outdated or never materialized. Check out the docs to know what’s in it or not. 👋