Its the motion of the ocean in the library that matters.
Riot – A React-like, 2.5K user interface library
71–80 of 222 posts
Re: Riot – A React-like, 2.5K user interface library
#72What has this been used on?
Re: Riot – A React-like, 2.5K user interface library
#73Re: Riot – A React-like, 2.5K user interface library
#74Hm. How does this compare to Mithril JS ( http://lhorie.github.io/mithril/ )? I just looked at the doc and read this thread (at 61 comments). Same: * virtual dom * has its own tag syntax * Mithril has MSX, but also supports regular JS data structure with m("tag", {attr:val, onclick: func, [more tags, "text"]} * router Different: * Where Mithril allows you to build and transform resulting template structure before vir…
Riot offers following to the (massive) client-side table:
1. Custom tags (with unscary HTML + JS syntax)
2. Minimalism (both size and API surface)
3. Performance (minimizing DOM operations with virtual DOM)
The 3rd item is not battle-tested / benchmarked yet and there is probably room for improvements.
Re: Riot – A React-like, 2.5K user interface library
#75For anyone who doesn't remember, Riot.js used to be a 1kb MVP library, https://news.ycombinator.com/item?id=7036274
Re: Riot – A React-like, 2.5K user interface library
#76Re: Riot – A React-like, 2.5K user interface library
#77Re: Riot – A React-like, 2.5K user interface library
#78Where is the list of controls? I would be really interested to see their grid layout control implementation. This is something web is struggling with.
Re: Riot – A React-like, 2.5K user interface library
#79Where is the list of controls? I would be really interested to see their grid layout control implementation. This is something web is struggling with.
Riot 2.0 is a "core" library and such controls can be build on top of it. No controls exist, since this is all very new.