> The idea that you're going to shove 1TB of data down to the client strikes me as slightly unhinged
Yeah which is why I asked for clarification from them because it seemed really weird to assert that as a positive for the app?
> It would be much faster, and, I think, simpler, to keep the data on a central server, have it generate the visualizations, and push them down to the client.
Yeah I completely agree but in this case, Mighty would have next to no advantage over just loading the visualization on your own machine. Hence, again the confusion about asserting Mighty as a means to an end
Yeah, agreed. I can see Mighty as perhaps being useful as a band-aid to deal with someone else's poor, resource-hungry design.
But if you're the actual app developer, I'm just not seeing a good reason why you would want to deliberately incorporate this technology into your design. Why farm the sever-side rendering out to a middleman when you could just... do server-side rendering?
Yeah which is why I asked for clarification from them because it seemed really weird to assert that as a positive for the app?
> It would be much faster, and, I think, simpler, to keep the data on a central server, have it generate the visualizations, and push them down to the client.
Yeah I completely agree but in this case, Mighty would have next to no advantage over just loading the visualization on your own machine. Hence, again the confusion about asserting Mighty as a means to an end