Writing an Operating System in 1,000 Lines (C)
https://github.com/nuta/operating-system-in-1000-lines?tab=readme-ov-file
https://github.com/nuta/operating-system-in-1000-lines?tab=readme-ov-file
GitHub
GitHub - nuta/operating-system-in-1000-lines: Writing an OS in 1,000 lines.
Writing an OS in 1,000 lines. Contribute to nuta/operating-system-in-1000-lines development by creating an account on GitHub.
π₯3π3
Comptime as Configuration (Zig)
https://www.openmymind.net/Comptime-as-Configuration/
https://www.openmymind.net/Comptime-as-Configuration/
www.openmymind.net
Comptime as Configuration
Karl Seguin's Blog - A mix of coding and creative writing
π3β€1
Be aware of the Makefile effect
https://blog.yossarian.net/2025/01/10/Be-aware-of-the-Makefile-effect
https://blog.yossarian.net/2025/01/10/Be-aware-of-the-Makefile-effect
blog.yossarian.net
Be aware of the Makefile effect
Nearly All Binary Searches and Mergesorts are Broken
https://research.google/blog/extra-extra-read-all-about-it-nearly-all-binary-searches-and-mergesorts-are-broken/
https://research.google/blog/extra-extra-read-all-about-it-nearly-all-binary-searches-and-mergesorts-are-broken/
research.google
Extra, Extra - Read All About It: Nearly All Binary Searches and Mergesorts are
Posted by Joshua Bloch, Software EngineerI remember vividly Jon Bentley's first Algorithms lecture at CMU, where he asked all of us incoming Ph.D. ...
π€―3π₯1π1π1π¦1
Getting silly with C
: C is beautiful yet full of horrors. Here's to uncovering its hidden depths.https://lcamtuf.substack.com/p/weekend-projects-getting-silly-with
Substack
Weekend projects: getting silly with C
C is beautiful yet full of horrors. Here's to uncovering its hidden depths.
π€―1
Memory error checking in C and C++
: Comparing Sanitizers and Valgrindhttps://developers.redhat.com/blog/2021/05/05/memory-error-checking-in-c-and-c-comparing-sanitizers-and-valgrind
Red Hat Developer
Memory error checking in C and C++: Comparing Sanitizers and Valgrind | Red Hat Developer
This article compares two tools, Sanitizers and Valgrind, that find memory bugs in programs written in memory-unsafe languages. These two tools work in very different ways. Therefore, while Sanitizers
π1
π¦3β€1π€―1
Four limitations of Rust's borrow checker
https://blog.polybdenum.com/2024/12/21/four-limitations-of-rust-s-borrow-checker.html
https://blog.polybdenum.com/2024/12/21/four-limitations-of-rust-s-borrow-checker.html
Considerations on Codecrafting
Four limitations of Rustβs borrow checker
Iβve been using Rust for hobby projects since 2016 and have been working professionally in Rust since 2021, so I tend to consider myself pretty knowledgeable about Rust. Iβm already familiar with all the common limitations of Rustβs type system and how toβ¦
π―3
doom.pdf
6.2 MB
Doom source port that runs inside a PDF file
https://github.com/ading2210/doompdf?tab=readme-ov-file
https://github.com/ading2210/doompdf?tab=readme-ov-file
π6π€―2π1
Advanced_Topics_in_Types_and_Programming_Languages.pdf
595.8 KB
Advanced Topics in Types and Programming Languages
: Typed Operational Reasoning (Chapter 7)π3
David A. Wheeler's Review of Debugging by David J. Agans
https://dwheeler.com/essays/debugging-agans.html
https://dwheeler.com/essays/debugging-agans.html
π1
SemVer Considered Harmful
https://jolynch.github.io/posts/semver_considered_harmful/
https://jolynch.github.io/posts/semver_considered_harmful/
π2π1
Async Rust is about concurrency, not (just) performance
https://kobzol.github.io/rust/2025/01/15/async-rust-is-about-concurrency.html
https://kobzol.github.io/rust/2025/01/15/async-rust-is-about-concurrency.html
Kobzolβs blog
Async Rust is about concurrency, not (just) performance
TLDR: I think that the primary benefit of async/await is that it lets us concisely express complex concurrency; any (potential) performance improvements are just a second-order effect. We should thus judge async primarily based on how it simplifies our codeβ¦
Improve Rust Compile Time by 108x
https://burn.dev/blog/improve-rust-compile-time-by-108x/
https://burn.dev/blog/improve-rust-compile-time-by-108x/
burn.dev
Improve Rust Compile Time by 108X
We started with a compilation time of 108 seconds for the matmul
benchmarks, which was reduced to only 1 second after all the
optimizations. The most effective optimization was the element-type
generics swap, where we instantiated generic functions with predefinedβ¦
benchmarks, which was reduced to only 1 second after all the
optimizations. The most effective optimization was the element-type
generics swap, where we instantiated generic functions with predefinedβ¦
π¦1
How I think about Zig and Rust
https://lewiscampbell.tech/blog/250117.html
https://lewiscampbell.tech/blog/250117.html
lewiscampbell.tech
How I think about Zig and Rust
21st century systems languages, with fundamentally different philosophies.
π₯5π5πΏ2π¦1
A minimalistic implementation of Refal (in Rust).
https://github.com/ilya-klyuchnikov/refal
https://github.com/ilya-klyuchnikov/refal
GitHub
GitHub - ilya-klyuchnikov/refal
Contribute to ilya-klyuchnikov/refal development by creating an account on GitHub.
π₯2