Boris Kaul

Thanks, uploaded 0.4.1 to the npm.

@vladimiry The only reason why I've used classes is to be able to identify this objects in the memory profiler. I don't like how I've implemented everything in this package...

@vladimiry optimizing compilers like [Google Closure Compiler](https://github.com/google/closure-compiler) are removing properties with `undefined` values when object is instantiated, so it will make all callsites that accessing this objects polymorphic. That is...

Just [checked](https://closure-compiler.appspot.com/home#code%3D%252F%252F%2520%253D%253DClosureCompiler%253D%253D%250A%252F%252F%2520%2540compilation_level%2520ADVANCED_OPTIMIZATIONS%250A%252F%252F%2520%2540output_file_name%2520default.js%250A%252F%252F%2520%253D%253D%252FClosureCompiler%253D%253D%250A%250A%252F%252F%2520ADD%2520YOUR%2520CODE%2520HERE%250A%252F**%250A%2520*%2520%2540constructor%250A%2520*%2520%2540final%250A%2520*%252F%250Afunction%2520F()%2520%257B%250A%2520%2520this.a%2520%253D%25200%253B%250A%2520%2520this.b%2520%253D%2520void%25200%253B%250A%2520%2520this.c%2520%253D%25201%253B%250A%257D%250Avar%2520A%2520%253D%2520%257B%2520a%253A%25200%252C%2520b%253A%2520void%25200%252C%2520c%253A%25201%2520%257D%253B%250A%250Aconsole.log(A)%253B%250Aconsole.log(new%2520F())%253B%250A%250A) latest GCC, and I can't reproduce this behavior on simple examples, so maybe it is ok. I had this problem 4 years ago.

> It's not an issue for pre-compiled/pre-bundled client apps. Just tried it with the latest webpack+terser, and it is still unable to deal with it and leaves alot of unused...

`ivi` doesn't support rendering into the `documentElement` or directly into `body` because there are [many issues](https://medium.com/@dan_abramov/two-weird-tricks-that-fix-react-7cf9bbdef375). One of the [major issues in Safari](https://trac.webkit.org/changeset/237978/webkit/) were fixed just recently, but there are...

> I suppose we can create some directives (like META, TITLE) to help with it but it doesn't looks clear. `useEffect()` hooks are ignored during SSR. ```ts const useDocumentTitle =...

On the server you can render entire page and it will ignore `useEffect` hook: ```ts const FullPage = (t: string) => ( html(_, _, [ meta(_, _, [ title(_, _,...

> the perf and ux benefits of hydrating rather than re-rendering are significant, and i have found 0 issues so far in doing it. It is not about hydrating vs...

> maybe if you're building photoshop or a 3d editor, then it is due to the massive amount of intricate state. This techniques were used even before React/isomorphic rendering on...