4 ms·
How about an immediate-mode renderer that works like a Rust async executor? The executor could run all of the rendering closures on one core and benefit from c
by mleonhard 6y ago
How about an immediate-mode renderer that works like a Rust async executor?
The executor could run all of the rendering closures on one core and benefit from caching.
It could detect slow rendering closures and automatically switch them to buffered mode and run them on a "slow renderers" thread. This would keep the rest of the UI snappy. It could also tint those portions of the UI so users can see which app is the culprit of UI slowness.
I hope that Rust can someday be used as the basis of an OS that does not rely on sandboxing for security, but instead uses the compiler to enforce security. Such an OS could use cooperative multitasking and use a lot less energy and less expensive hardware than our current multi-core CPU + MMU + kernel ring model.
- voodootrucker 6y agoI was trying to write this while learning Rust: https://github.com/avantgardnerio/rsui https://github.com/avantgardnerio/rsui I now have some production experience in Rust and have learned to shy away from Piston. I think you've inspired me to try again with SDL2 and a better approach.
- nitrogen 6y agoTo use the compiler for security you would need a way to prove that a given piece of machine code was generated by a trustworthy compiler, and not modified after it was loaded.
- mleonhard 6y agoYes. The idea is that all software is distributed as source code. The OS compiles the software itself. To prevent software modification, we need a new CPU with two memory controllers, one for data and one for code. The code memory controller can only read, not write. A separate CPU runs the compiler and writes the code RAM.