Serhii Khoma

not exactly, I propose to extract instances to separate files, so that they can be reused across compiled modules e.g. `../instances_cache/eq_Array_String.js` can be reused in `output/Foo/index.js` and `output/Bar/index.js`

Yes, so we can: 1. reuse instances within functions #3915 2. reuse instances within file (rhendic proposal) 3. reuse instances within whole program (this issue) 3.1. for `purs compile`/ not...

even better the content should be a `Text`, not array of Nodes as per https://www.w3.org/TR/html52/sec-forms.html#the-textarea-element ``` Content model: Text. ```

ah, then, probably, nothing should be changed

> The fact the prop/attribute distinction exists at all still bothers me agree maybe dom-indexed should split attributes and props currenly ``` type HTMLtextarea = Interactive ( autofocus :: Boolean...

> I guess this is something that needs special handling for hydration / vdom-text-rendering. :+1: I think as long as everyone are using the `value` function from halogen that is...

> I cannot replicate the second problem you report, could you share a repo with instructions on how to replicate this? Also a gist or a series of commands could...

:+1: for mentioning type classes Also we can use coverage tool that shows how frequently each line is called Probably https://istanbul.js.org/docs/advanced/coverage-object-report/ https://medium.com/@nikjohn/now-code-coverage-directly-on-chrome-devtools-e8177a25c7ef

sure, after hydration is finished

here is an example ```purs module Server where import Prelude import Effect import Effect.Aff import Effect.Aff.Class (liftAff, class MonadAff) import Data.Tuple (Tuple(Tuple)) import Control.Monad.Indexed.Qualified as IndexedMonad import Hyper.Node.FileServer as Hyper...