<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Programming on Rohit Garg</title><link>https://rohit-garg.me/tags/programming/</link><description>Recent content in Programming on Rohit Garg</description><generator>Hugo</generator><language>en</language><copyright>© Rohit Garg</copyright><lastBuildDate>Sat, 13 Jun 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://rohit-garg.me/tags/programming/index.xml" rel="self" type="application/rss+xml"/><item><title>What Really Happens When You Run a Program?</title><link>https://rohit-garg.me/how-os-executes-program/</link><pubDate>Sat, 13 Jun 2026 10:00:00 +0530</pubDate><guid>https://rohit-garg.me/how-os-executes-program/</guid><description>&lt;p>A program sitting on disk is not alive yet.&lt;/p>
&lt;p>It may contain valid machine instructions, static data, library information, and an entry point. But until the operating system gives it memory, a process identity, CPU time, and a way to talk to the outside world, it is just bytes in a file.&lt;/p></description></item></channel></rss>