One limitation of the supersize UI is that it needs to convert .size files into a newline delimited JSON format before symbols can be read in the application. Currently, this is done using a python command on a user's locale machine. It would be ideal if the UI could handle this itself, allowing for .size files to be uploaded directly.
There are three potential avenues to take:
a) Port all of Super Size's python logic to Javascript.
b) Compile the python program & runtime into WebAssembly.
c) Run a python server that accepts .size files and returns .ndjson files via a REST API.
Option C seems to be the most ideal. The server would accept .size files either via URL or by POST data, and would return an .ndjson file as a response. The UI could hook into the REST API and allow for .size files to be uploaded directly.
This would also avoid the need to pregenerate milestone reports.
Comment 1 by estevenson@chromium.org
, Sep 27