3 ms·
So... it's mithril with a ton of the useful stuff ripped out, for a comparatively tiny reduction in size? Why would I want that?
by qwertyuiop924 10y ago
So... it's mithril with a ton of the useful stuff ripped out, for a comparatively tiny reduction in size? Why would I want that?
- erikpukinskis 10y agoThere 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.
- qwertyuiop924 10y agoThe 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.
- erikpukinskis 10y agoOne man's tight integration is another man's tight coupling.
- qwertyuiop924 10y agoYou 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.
- johangorter 10y agoWe wouldn't have created Maquette if Mithril supported animated transitions (in an unobtrusive manner). So that is the real difference.
- qwertyuiop924 10y agoMithril does that decently, actually. I mean, the library's not included, but it's not too hard: http://lhorie.github.io/mithril-blog/velocity-animations-in-mithril.html http://lhorie.github.io/mithril-blog/velocity-animations-in-...