Daniel Weck

Thanks @iherman I will look into this. At first glance, the use of multiple `source` elements instead of the `src` attribute introduces some additional complexity (parser / generator + asset...

@iherman That's correct, support for video asset handling is missing entirely (`src` attribute and `source` elements).

> A perfect hash function will always create the same class names in order and prevent collisions, I have been using this little hash routine borrowed from `csstag` (similar project...

I like the typo `IDPDF` (vs. ` IDPF`) ... Freudian slip? ;o)

> A variant of this that provides subsetted `hydrate(vnode, parent, children)` and `render(vnode, parent, children)` can be found here: > https://gist.github.com/developit/f321a9ef092ad39f54f8d7c8f99eb29a @jaydenseric also see Jason's other Gist: https://gist.github.com/developit/f4c67a2ede71dc2fab7f357f39cff28c

Wow that's really nice. I have been using Valtio by @dai-shi in one of my side projects (pure Preact, not preact/compat). I have really enjoyed the DX and UX benefits...

Optional chaining support: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining

Turborepo should ease the pain: https://github.com/vercel/turborepo

In the spirit of open-source, I wrote my own piece here: https://github.com/edrlab/thorium-reader/issues/1375 Food for thoughts :)

Follow up: https://github.com/developit/preact-markup/issues/6#issuecomment-809934523