Conversation

Notices

1. Machismo (zerglingman@freespeechextremist.com)'s status on Saturday, 09-Dec-2023 23:14:15 JST Machismo

   • Moon
   • NEETzsche
   • rees
   @Moon @rees @NEETzsche >concurrency
   >meme
   Isn't that just a meme name for threading? Of course threading's great, until you accidentally create a race condition.
   • NEETzsche (neetzsche@iddqd.social)'s status on Saturday, 09-Dec-2023 23:17:06 JST NEETzsche

     in reply to

     • Moon
     • rees

     I had an entire course in college about multithreaded programming but what made that class cool is that they let undergraduates like me use the supercomputer to crunch mad numbers with CUDA. The jobs were designed to run for 30min and you had carte blanche. Half of us wrote BitCoin miners and SHA hash crackers. Shit was so cash, even though the SHA hash crackers didn’t work lol

     Machismo likes this.
   • rees (rees@breastmilk.club)'s status on Saturday, 09-Dec-2023 23:19:18 JST rees

     in reply to

     • Moon
     • NEETzsche
     @NEETzsche @Zerglingman @Moon I linked you to a study (and pete, got no replies) on rust creating sound code for kernels
     
     https://dl.acm.org/doi/10.1145/3623759.3624554
     >The memory-safe systems programming language Rust is gaining more and more attention in the operating system development communities, as it provides memory safety without sacrificing performance or control. However, these safety guarantees only apply to the safe subset of Rust, while bare-metal programming requires some parts of the program to be written in unsafe Rust. Writing abstractions for these parts of the software that are sound, meaning that they guarantee the absence of undefined behavior and thus uphold the invariants of safe Rust, can be challenging. Producing sound code, however, is essential to avoid breakage when the code is used in new ways or the compiler behavior changes.
     >In this paper, we present common patterns of unsound abstractions derived from the experience of reworking soundness in our kernel. During this process, we were able to remove over 400 unsafe expressions while discovering and fixing several hard-to-spot concurrency bugs along the way.
     Machismo likes this.
   • NEETzsche (neetzsche@iddqd.social)'s status on Saturday, 09-Dec-2023 23:19:55 JST NEETzsche

     in reply to

     • Moon
     • rees

     Why do I care about this?

     Machismo likes this.
   • rees (rees@breastmilk.club)'s status on Saturday, 09-Dec-2023 23:20:08 JST rees

     in reply to

     • Moon
     • NEETzsche
     @NEETzsche @Zerglingman @Moon >During this process, we were able to remove over 400 unsafe expressions while discovering and fixing several hard-to-spot concurrency bugs along the way.
     Machismo likes this.
   • NEETzsche (neetzsche@iddqd.social)'s status on Saturday, 09-Dec-2023 23:22:27 JST NEETzsche

     in reply to

     • Moon
     • rees

     Okay. So you’re saying I should learn Rust because in doing so it will help me retard-proof future projects?

     Machismo likes this.
   • rees (rees@breastmilk.club)'s status on Saturday, 09-Dec-2023 23:23:54 JST rees

     in reply to

     • Moon
     • NEETzsche
     @NEETzsche @Zerglingman @Moon that's one reason, I actually find it quicker to prototype in rust than javascript at times
     Machismo likes this.