<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software Security on The Coders Blog</title><link>https://thecodersblog.com/tag/software-security/</link><description>Recent content in Software Security on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 01 May 2026 21:06:31 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/software-security/index.xml" rel="self" type="application/rss+xml"/><item><title>Lib0xc: Microsoft's Bid to Make C Systems Programming Safer in 2026</title><link>https://thecodersblog.com/lib0xc-microsoft-s-c-apis-for-safer-systems-programming-2026/</link><pubDate>Fri, 01 May 2026 21:06:31 +0000</pubDate><guid>https://thecodersblog.com/lib0xc-microsoft-s-c-apis-for-safer-systems-programming-2026/</guid><description>&lt;p&gt;Memory corruption bugs continue to plague critical C systems, driving many to declare the language fundamentally broken for modern use. But what if the answer isn&amp;rsquo;t always a wholesale rewrite in Rust, but a smarter, more disciplined approach to C itself?&lt;/p&gt;
&lt;h2 id="the-enduring-paradox-why-c-persists-and-persists-with-risk"&gt;The Enduring Paradox: Why C Persists (and Persists with Risk)&lt;/h2&gt;
&lt;p&gt;The pervasive reality of systems programming highlights C&amp;rsquo;s unparalleled performance, direct hardware access, and minimal runtime overhead. These attributes remain indispensable for operating systems, embedded systems, and high-performance computing, where every byte and cycle counts. C isn&amp;rsquo;t going anywhere, and senior C/C++ developers know this intimately.&lt;/p&gt;</description></item></channel></rss>