Heavy Networking 652: Why Networkers Should Want Routing Protocols Written In Rustlang

On today’s Heavy Networking episode, I talk with Nick Carter about Flock Networks, his routing protocol stack startup, as well as Nick’s love of the Rust programming language. As a network engineer, maybe you don’t think you care about Rust. After all, you’re not writing the code, so what difference does it make to you how the BGP daemon you’re running was developed? Nick’s here to explain why the discerning network engineer might prefer their routing daemons to have been written in Rust. And certainly he’s got the background. He was a network engineer and CCIE before he was a programmer, so he feels our pain. But…I’ll let him tell that story. We discuss: * Why Nick wrote a new routing stack * The Rust language and why Nick chose it * Rust vs. C and C++ * Whether it matters what language your routing stack was written in * The Flock routing protocol * Flock features and capabilities * More Sponsor: ITProTV Start or grow your IT career with online training with ITProTV. Learn IT, pass your certs, and get a great job! Visit itpro.tv/packetpushers and use the promo code PACKETPUSHERS at checkout to get 30% off all plans. Show Links: Flocknetworks.com [email protected] Flock Networks on LinkedIn @flocknetworks – Flock Networks on Twitter Merge tag ‘rust-v6.1-rc1’ of https://github.com/Rust-for-Linux/linux