You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This software is a single-page JavaScript application, which means it's ready-built version should hardly be larger than what can be transferred from server to browser in a reasonable time – let's say 2-3 MiB at the most. This is esp. true since all the large JSON files with graph data etc. do not reside here but are loaded on demand from Graphryder API. Instead, what we have is 165 MiB of stuff, and the total installation incl. build environment and Linkurious.js is even 646 MiB: 😮 😮 😮
$ du -hsc *# Most significant lines only …
…
3.6M app
38M bower_components
…
165M dist
…
136M linkurious
303M node_modules
…
646M total
Now software size is a proxy for complexity, and with complexity come maintenance nightmares, security nightmares and other such things. So this situation is unacceptable by every standard for production software with a handful of features like this one. (Notably, this software was not meant to be production software so far, but rather a prototype.)
I just checked: a full reload of the Graphryder Dashboard frontpage is 2.4 MiB uncompressed, excluding the JSON data served by Graphryder API. About reasonable. So most of the other stuff in ./dist/ will just be useless clutter that can be removed in one way or another. For example, I saw a complete Bootstrap API documentation in there.
The text was updated successfully, but these errors were encountered:
This software is a single-page JavaScript application, which means it's ready-built version should hardly be larger than what can be transferred from server to browser in a reasonable time – let's say 2-3 MiB at the most. This is esp. true since all the large JSON files with graph data etc. do not reside here but are loaded on demand from Graphryder API. Instead, what we have is 165 MiB of stuff, and the total installation incl. build environment and Linkurious.js is even 646 MiB: 😮 😮 😮
Now software size is a proxy for complexity, and with complexity come maintenance nightmares, security nightmares and other such things. So this situation is unacceptable by every standard for production software with a handful of features like this one. (Notably, this software was not meant to be production software so far, but rather a prototype.)
I just checked: a full reload of the Graphryder Dashboard frontpage is 2.4 MiB uncompressed, excluding the JSON data served by Graphryder API. About reasonable. So most of the other stuff in
./dist/
will just be useless clutter that can be removed in one way or another. For example, I saw a complete Bootstrap API documentation in there.The text was updated successfully, but these errors were encountered: