4 ms·
It's not, no. But it's also very easy to write alloc C# code and people will if you give them the option. That won't be possible in Rust / C.
by chrisandchris 3y ago
It's not, no. But it's also very easy to write alloc C# code and people will if you give them the option. That won't be possible in Rust / C.
- charcircuit 3y agoEven so 16.666 ms is a lot of time for just handling mouse input.
- satvikpendem 3y agoAttitudes like these is how we eventually end up with bloated messes like Electron. Performance matters, everywhere. Some of us increasingly also use monitors with more than 60 hertz.
- mkl 3y agoThe CPU has other things to do too.
- charcircuit 3y agoNo matter what you do the CPU will always have other stuff to do.
- IshKebab 3y agoSo you agree...
- RetroTechie 3y agoYes. 640 usec should be enough for every mouse.
- davikr 3y agoIt's also very easy to write alloc C++ code, no?
- jayd16 3y agoThis is pretty silly. They have the option to alloc and leak in C too. Rust is also just guaranteed memory safety not leak free, right? In a competition of lazy code, I'd rather GC pauses than OOM crashes. But C# isn't ideal for a driver because of the weight of the runtime not because it's hard to save on allocations.
- steveklabnik 3y agoIt is correct that Rust does not (nor claim to) solve memory leaks.