/explore
|
You are here 
|
noteflakes.com | ||
| | | | |
nikgrozev.com
Most software engineers know about operating system (OS) level processes and threads. They are taught in all university OS courses. However, newer concepts p... |
|
| | | | | ||
| | | | |
www.codeotaku.com
[AI summary] The post presents a final report on implementing a lightweight per-thread fiber scheduler in Ruby to improve concurrency and parallelism while minimizing changes to existing code. |
|
| | | | | ||
| | | | |
byroot.github.io
I want to write a post about Pitchfork, explaining where it comes from, why it is like it is, and how I see its future. But before I can get to that, I think I need to explain a few things, namely why in many circles fork is seen as a relic of the past, if not outright the devil's creation. And yet, it's ubiquitous in the Ruby ecosystem. |
|
| | | | | ||
| | | | |
blog.polybdenum.com
One of the first things any Rust programmer learns is that you can't pass an object and a reference to that object around at the same time. It's impossible to do, even indirectly. This limitation has been the subject of countless questions on Stack Overflow and posts on Reddit and the Rust forums and anywhere else where Rust programmers might ask for help. It's so well-known that most people treat it like an axiom, not just a limitation of Rust as it currently exists, but an inherent limitation of borrow checking in general. |
|
| | | |||
