Maquette – Pure and simple virtual DOM library

Re:Maquette – Pure and simple virtual DOM library by erikpukinskis on Monday August 29, 2016 @05:32PM (#12385540)

There is something to be said for using APIs whose total surface area is close to the surface area that you need. If I want to use different parts of three libraries, but those libraries have excess functionality with a lot of overlap, then I have to deal with potentially conflicting expectations. I also have to worry that the subset of functionality I do use will go away or change because it's not the central focus of the library.

[ Parent | on HN ]

Re:Maquette – Pure and simple virtual DOM library by qwertyuiop924 on Monday August 29, 2016 @06:42PM (#12386043)

The thing is, if you're using a VDOM, you'll probably want the other stuff Mithril's got anyways. And the tight integration with the vdom renderer helps make sure that rerenders happen only when something actually changes, and that partial states don't render. For 3 megs, I'll take it.

[ Parent | on HN ]

Re:Maquette – Pure and simple virtual DOM library by erikpukinskis on Monday September 05, 2016 @01:56PM (#12431458)

One man's tight integration is another man's tight coupling.

[ Parent | on HN ]

Re:Maquette – Pure and simple virtual DOM library by qwertyuiop924 on Friday September 09, 2016 @03:22PM (#12465319)

You can actually disable a lot of that stuff. It's just like that by default. You can even write your own render loop, if you really want to.

[ Parent | on HN ]