After an initial "sprint" (a block of days I've been able to allocate to Enliven dev), I've only been able to work on it on and off hence the slow pace of development.
Locally I've been refactoring and learning from the initial code burst. I've been experimenting too, especially with several flavors of encoding composition:
- pre-rendering constant parts as bytes
- pre-rendering constant parts as gzipped bytes (moderate success: it works but needs work to, at least, trigger this only on constant strings above a given threshold)
- pre-rendering constant parts as direct bytebuffers and rendering the whole template as an array of bytebuffers to leverage vectored IO (aka gather IO)
However the current goal is to add dynamic (reactive) templating.
From an abstract point of view I try to make Enliven's core a meta templating system. (Currently there's only static html and static text.)