Idea: Dismantle, repurpose, transfer, reuse?

Instead of reusing Ultradom in Hyperapp (which is totally possible, but a bit awkward in my opinion) what if Hyperapp exported its patch function instead?

import { h, patch } from "hyperapp"

// Use h & patch as you normally would in Ultradom.

Thanks to tree-shaking, dependents of Ultradom will not need to include Hyperapp’s state management portion. 🎉

My intention is to reuse code and remove the burden of maintaining both Hyperapp and Ultradom when their respective virtual DOM implementations are virtually (pun intended) the same.

---

So, what would happen to Ultradom? Good question. I don’t know. Perhaps I could use it for experiments, a more sophisticated virtual DOM implementation, a new framework, library, etc.

What do you think?

[rbiggs]

Enabling the export of patch from Hyperapp would eliminate the reason for Ultradom. One less library to maintain. 😃

[frenzzy]

State management is already available via app function. Proof of concept: https://github.com/Swizz/hyperapp-term-poc So, I also think it is not necessary to expose something more. Just h, app and patch is enough.