Can current Unity to Webgl exports compete with D3 or Three.js for real-time data visualizations?
-performance?
-code file size?
Can current Unity to Webgl exports compete with D3 or Three.js for real-time data visualizations?
-performance?
-code file size?
This depends on what āreal-time data visualizationā means for you. If you are speaking about just a dashboard with some graphs, blinken lights and some 3D then both of these would win in your two categories.
If you start doing some wild out there 3D stuff for your visualization that actually uses many of our 3D features then Unity will probably be in the race again.
Assuming you donāt care about other features like our editor, audio, etc.
Thanks. I need to do my own tests but was wondering if you had an idea how much ācode overheadā or increased file size I can expect with a Unity>WebGL export vs creating directly in Three.JS?
Never used either myself but from the looks of the examples creating some dashboard graphs are just a few lines of code with them. Just try it yourself and create a small graph in C#, export to webGL (make sure to remove all non-essential components from the scene) and compare against the size in D3.