<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>MIT License on Siva Kalidasan</title>
    <link>https://mksiva.com/tags/mit-license/</link>
    <description>Recent content in MIT License on Siva Kalidasan</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 30 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://mksiva.com/tags/mit-license/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MIT vs. Apache 2.0: At a Glance</title>
      <link>https://mksiva.com/tech/mit-vs-apache-2-0-at-a-glance/</link>
      <pubDate>Tue, 30 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://mksiva.com/tech/mit-vs-apache-2-0-at-a-glance/</guid>
      <description>&lt;p&gt;&lt;em&gt;MIT and Apache 2.0 are two of the most popular open-source licenses. Both are friendly to developers and businesses — but they are not identical. Here is a simple side-by-side look.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&#34;why-this-matters&#34;&gt;Why this matters&lt;/h2&gt;
&lt;p&gt;When you use open-source software — or when you publish your own — you are agreeing to a &lt;strong&gt;license&lt;/strong&gt;. A license answers practical questions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Can I use this at work?&lt;/li&gt;
&lt;li&gt;Can I change it?&lt;/li&gt;
&lt;li&gt;Can I ship it inside a paid product?&lt;/li&gt;
&lt;li&gt;What text do I need to keep when I redistribute it?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;MIT&lt;/strong&gt; and &lt;strong&gt;Apache License 2.0&lt;/strong&gt; are both &lt;strong&gt;permissive&lt;/strong&gt; licenses. That means you can use the code in almost any project, including commercial and closed-source products, as long as you follow a few simple rules.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
