Conversation
Jarkko Sakkinen
jarkko
Edited 3 hours ago
Tracker will take some time and especially since I'm doing C rewrite, which is right now completely broken (literally a start from scratch).
However, the elegant C implementation will motivate me more as a developer as I enjoy it more, and thus will eventually get the project there.
With Rust implementation I know I would give up at some point. E.g., in this type of project you want to leave space for downscaling to very low-end computers, and more towards 80s/90s hardware we go, more opcodes cost relative to memory access costs. Thus I don't want compiler to do any memory safety stuff for instance. Software must have full control of generated opcodes.
The code base looks in style a lot like kernel code and utilizes its popular patterns such as ops structs and container_of macros. And coding style is of course kernel coding style.
However, the elegant C implementation will motivate me more as a developer as I enjoy it more, and thus will eventually get the project there.
With Rust implementation I know I would give up at some point. E.g., in this type of project you want to leave space for downscaling to very low-end computers, and more towards 80s/90s hardware we go, more opcodes cost relative to memory access costs. Thus I don't want compiler to do any memory safety stuff for instance. Software must have full control of generated opcodes.
The code base looks in style a lot like kernel code and utilizes its popular patterns such as ops structs and container_of macros. And coding style is of course kernel coding style.
1
0
0
Project reset/migration to C code base started over weekend when my friend asked could we do (G3/G4) PowerPC port of the engine. I don't know but I don't want to create bottleneck preventing such work :-)
Being aware of such potential bottleneck I had no other options really.
Being aware of such potential bottleneck I had no other options really.
0
0
0