The JS ecosystem is a mess - I'm sure many of us will agree regarding that sentiment.
I'd like to gather thoughts about Nim's current FE web libraries and if we think we should expand upon them further... Most people, who have built a website in the past half-decade are familiar with react and angular. Not to lump all FE web libraries into one category - but these libraries tend to rely on an implementation of a Virtual DOM and then an algorithm to diff between the virtual DOM and the actual DOM. The reason this is done in the first place, is to help eliminate inconsistencies between app state and ui state. More recently, a few libraries have emerged - [https://github.com/WebReflection/hyperHTML](https://github.com/WebReflection/hyperHTML) and [https://github.com/Polymer/lit-html](https://github.com/Polymer/lit-html) These libraries are focused on the web component specs, which if you're not familiar with, are a different beast all together - [https://www.webcomponents.org/specs](https://www.webcomponents.org/specs) React and web components are not 1:1 - for instance, web components don't offer a solution to application state management or even local component state - in fact they don't define components, they define custom HTML elements. Still - you can build upon these specs to define your own custom elements, and then add glue to a state management library like redux or mobx or what have you... I guess the question being asked here is - Is Karax sufficient? Would it be better if it was extended to support template literals so that you could take advantage of some of the performance benefits purported by hyperHTML / lit-html? Does anyone care?
