>>907534
>open source but actually having manageable code instead of 10 billion lines of bloat
>for example knowing how your text system works instead of lol I use utf8 with 500 text rendering libraries and hardware acceleration throughout the stack
I like this.
How can we make it easier to follow a project's code's data flow, so that people's capacity to review it on their own, without having to trust other parties, is maximized, as in the libre ideal of software security?
IDE-s already offer tooltip-like visualizations of functions' parametres and call stacks and data structures.
The only other ideas I have:
* An execution framework/sandbox integrated into the OS that would sort runtime function calls by frequency of execution, so that parts of the project that are most/least often used can be identified and inspected as suits one?
* An authoritative centre of implementations of common algorithms, which would be referenced, reviewed, and commented by everyone? (This is just libraries, I suppose.)
* Or oppositely, some kind of distributed system in which individual code units (functions, files, modules) may be vouched for by people using personal keys or whatever?
* Some kind of identification of code which contains literals, offering that code for review before all others? Demanding that literals be shipped in complete separation from algorithms within a project's source?
Those ideas are extremely stupid. They aren't meant to stand on their own, but rather hope to inspire others.