I agree. The difference in size is not that great, and the absolute sizes are small compared to the other things that have to go over the wire.
Either Riot or React would be fine, although I would be a bit concerned about the long-term future of Riot as it is supported by such a tiny company. More important is whether there are any off-the-shelf components for working with D3. One other thing to discuss: whether to target only ECMAScript 6 browsers. I'd say yes: it is so much easier to program in it and, at this point, we would not lose many potential end-users. Chrome and FireFox have supported most features for a long time. Safari's support is more recent, but complete. -tk On Sat, Jan 7, 2017 at 3:35 PM, Chris Matteri <[email protected]> wrote: > It doesn't seem like the size of React would be such an issue (10 kB for > Riot vs 45 kB for React, from the Riot website). I suspect that React's > boilerplate and explicit handling of state/dataflow help make large apps > more consistent and easier to debug. I also like how JSX feels like HTML > and Javascript (it doesn't introduce new syntax), though that's of lesser > importance. Certainly the community around React is larger, which means > more libraries, tooling, etc. > > I'll take a look at your comparison of plotting tools. So far I only know > about raw D3. > > You could implement just about anything in canvas, but the performance > benefits of canvas are probably not worth the increased complexity, so I > agree that SVG should be used. > > On Sat, Jan 7, 2017 at 2:09 PM, Thomas Keffer <[email protected]> wrote: > >> react too heavyweight? Wow! Remind me never to go backpacking with you. >> :-) >> >> -tk >> >> On Sat, Jan 7, 2017 at 10:13 AM, mwall <[email protected]> >> wrote: >> >>> chris, >>> >>> angular (1 or 2) has way too much overhead >>> >>> react is more heavyweight than i would like as well >>> >>> i lean toward riot: >>> >>> http://riotjs.com/ >>> >>> if you're going to do dashboards right, you either need a dashboard >>> framework that can do everything, or you need a bunch of components that >>> play well together and don't get in your way, either when you are building >>> or maintaining. >>> >>> since the former will never be true, i gravitate toward the latter. >>> >>> right now that means some d3-based plotting tool that can talk to influx >>> (or weert), a dials/gauges library (e.g., http://justgage.com/), a >>> sparkline library, and a reasonable ui-controls library (e.g., riot). use >>> them with jquery and bootstrap on the front end, and websockets on the >>> 'back' end. >>> >>> m >>> >> >> >
