Rage Against the State Machine

Weird Expressions and Where to Find Them

This is a written transcript of my RustConf 2022 talk using rustc at commit 6491eb1e6c9fac20faad11e5da16db3185b2410d You can find the video of the talk here. Introduction My name is Michael Gattozzi and today I want to bring you on a journey from "What?" to "No way that works" to "Wait why

Rust and it's Orphan Rules

Recently at work I managed to hit the Orphan Rules implementing some things for an internal crate. Orphan Rules you say? These are ancient rules passed down from the before times (pre 1.0) that have to do with trait coherence. Mainly, if you and I both implement a trait

Rust's Runtime

Rust has a runtime. No really it does! I blew past that aspect in my most recent post "Oxidizing the technical interview" [https://blog.mgattozzi.dev/oxidizing-the-technical-interview/] when I put in the line: > The greatest trick the Devil ever played was convincing C and Rust programmers their language has no

Oxidizing the technical interview

Inspired by Reversing the technical interview [https://aphyr.com/posts/340-reversing-the-technical-interview] and Hexing the technical interview [https://aphyr.com/posts/341-hexing-the-technical-interview] Years ago, as a young'in from the Rust Belt, you dreamed of becoming a systems programmer, an Abyss Gazer if you will. You wanted to live, breathe, and die

Rust and the case for WebAssembly in 2018

Every now and then a technology comes around that fundamentally changes the game and how things work. Java and the JVM created a world where the idea of portable code execution was possible, "compile once, run anywhere" (as long as there was a JVM available). JavaScript changed how the web