Conversation
Jarkko Sakkinen
jarkko
Now it is time phase out doing this and detach myself from the grip of hyperfocus ...
https://lore.kernel.org/rust-for-linux/aKUTF6lu5JetDJxX@kernel.org/T/#u
Ton of stuff that I did not do during last three weeks that I should had done (mainly outside of work) so navigating myself to that direction :-) I just could not stop, once I got really started.
Also I sleeping might be good idea once in a while :-)
#linux #kernel #tpm #rust
https://lore.kernel.org/rust-for-linux/aKUTF6lu5JetDJxX@kernel.org/T/#u
Ton of stuff that I did not do during last three weeks that I should had done (mainly outside of work) so navigating myself to that direction :-) I just could not stop, once I got really started.
Also I sleeping might be good idea once in a while :-)
#linux #kernel #tpm #rust
1
1
5
@jarkko looks like you earned a nap just for writing the notes.
1
0
1
@Netux It has been for me problematic to understand why we care about Rust because trivial memory errors are not something we would need a whole new language ecosystem. It's really this ability compose/decompose data that matters in Rust for kernel IMHO. In quite many categories of drivers it would take them to the next level if they could look more than just "max length" or similar attributes. Wanted to write it down while I had the thought on my mind :-)
1
0
1
@jarkko nice. I haven't jumped into the rust bandwagon. I'm mostly just python these days because work, and trying to wrap my head around erlang.
My C/C++ is about on par with a good college kid, so I doubt I'll ever get to a point where moving to rust will do me much good. More of a read and modify minor stuff for C than I'm likely to pull it out for new work.
0
0
0