Andrea Giammarchi

Imho the current proposal and polyfill works like a charm already and if a library wants to expose a read-only signal it has already the primitive to do so: `Signal.Computed`:...

interestingly enough, the good'ol String only based version (no uhtml/dom involved) was actually twice as fast (expected, but thanks for letting me measure that). 

My [pull request](https://github.com/felixfbecker/node-sql-template-strings/pull/104) would allow the following: ```js // example (no idea what prepareSet would do) const prepareSet = obj => SQL`preparedName = ${obj.key}`; // auto back-tick escaping of single/double...

@rightaway @skyjur My [current PR](https://github.com/felixfbecker/node-sql-template-strings/pull/104) would allow the following transformation: ```js SQL` UPDATE thetable SET thecolumn1 = null, "${'othercolumn' + version}`" = null WHERE id = ${id} ` ``` will...

nothing I can do until mid February, sorry

correction: until end of February (I still don't have my RPi with me)

> Am I right that viperhtml currently is missing any kind of documentation as well? Beside understanding the differences between DOM Level 0 and Level 3 events, viperhtml is basically...

so ... in the getting started I am creating, I have this server side `index.js` inside the `server` folder: ```js 'use strict'; // core const path = require('path'); // dependencies...

this module was a PoC for a proposal ... it's not super tested neither usable in production, imho, so it's possible it has bugs but I won't probably fix those

not sure I understand what you are doing, or why I would need another env to test a bug, but I can tell you I have pretty much zero time...