Re:A Not-Called Function Can Cause a 5X Slowdown
by phaedrus on Tuesday December 04, 2018 @11:06AM
(#18600633)
Imagine if the provenance of every code line or machine instruction was tracked all the way from what the human wrote to what the machine executes. Combined with data flow analysis, itself combined with runtime analysis via a feedback process like Profile Guided Optimization.
The outcome would be somewhat like a package management tool, but one which can subdivide & prune a package even if the original author wrote it monolithically.
It could also provide feedback in the IDE showing which lines are "dead code" that don't contribute to the features which you've declared (via tests) are important.
Re:A Not-Called Function Can Cause a 5X Slowdown
by tenaciousDaniel on Tuesday December 04, 2018 @11:04AM
(#18600611)
Yeah I agree. What OP is describing would require an architectural shift in the way npm packages are built, IMO.
Sidenote, this is related, and pretty interesting: https://npm.anvaka.com
Bit of a goose, though. As in, not sure it'll fly in its current (scrambled eggs) state. Perhaps a rewrite is really what's needed .. or maybe HaikuOS can deliver this without much ruffling of feathers?