Pavel Nuzhdin

I don't think Karax needs to have weird refs because it currently has `VNode.dom` which is much better and generates less boilerplate code. See my changes which replace `getElementById` usage...

Also, we have some closure traps related to Karax smart diff algorithm https://gist.github.com/pnuzhdin/ceb35356e88f4f0a865c829d9a05fc97 but I don't think that having `VNode` in a closure will lead to an issue because new...

Also, why you think `getElementById` depends on the DOM size? It seems it's hashtable so O(1) for a lookup. I've found the following benchmark which shows almost the same result...

> What if the resizer elements becomes model dependent? Would the view logic itself start to do diffing to determine whether it is necessary to create a new VNode? Not...

Also, `jsrutils` misses following: ```nim proc `&`*(s: float): cstring {.importcpp: "((#)+'')", nodecl.} ``` You may want to add it in the same time.

@flyingpie sure, here it is [windows-terminal-quake.zip](https://github.com/flyingpie/windows-terminal-quake/files/6595548/windows-terminal-quake.zip)