uhtml VS use-memo-one

I have to say that I am an extremist minimalist, so I use a nano-framework I developed for the frontend, with uhtml (https://github.com/WebReflection/uhtml) and some JavaScript libraries to help.

One of the main decisions I had to make early on was template handling, there are many approaches out there and of course, with React being the king, I first tried implementing a VirtualDOM complete with JSX support and whatnot... well that didn't really worked for what I was trying to achieve, so I moved into Tagged Template Literals (through µhtml) and tried to stick to standards as much as possible by building on top of the Custom Elements API.

Challenge: With declarative rendering, oftentimes entire DOM trees are re-painted because of simple prop or state changes that could have been handled faster by imperative DOM manipulation. I wanted a framework that, like Lit, only updated content or attributes that had changed instead of re-painting entire DOM elements and trees. Solution: I chose µhtml for the default templating system because it accomplishes this goal and other advanced templating features in a tiny bundle size. To make rendering even faster and smoother, I throttled uhtml's rendering using requestAnimationFrame.

> There are lighter-weight shadow dom frameworks out there (than Vue/React/Angular) so why would you want to write one yourself?

You can even avoid a shadow DOM entirely:

https://github.com/WebReflection/domdiff

https://github.com/WebReflection/uhtml

My next goal would be to discard snabbdom (and virtualdom) and use custom elements. For that I'm evaluating a library like https://github.com/WebReflection/uhtml and all it's ecosystem of utility

A tiny dom lib like https://github.com/WebReflection/uhtml is more than enough for very complicated UI, with understanding how events work, will be able to implement very thin state management on top. With game programming styled manual render() call here and there as needed, pretty neat.

Svelte separates its code between create and update lifecycles. Solid takes that one step further hoisting the DOM creation into clone-able Template elements that create whole portions of the DOM in a single call, incidentally a runtime technique used by Tagged Template Literal libraries like @webreflection 's uhtml and Lit.

I do not see this happens with https://github.com/WebReflection/uhtml/blob/master/DOCUMENTA... family. They are around for quite awhile, and their philosophy is clear from start, do one thing well, small and no tooling.

We create an Apollo client instance with our own createApolloClient function and memoize it with useMemoOne, ensuring a semantic guarantee of memoization.