Open Source: The Free Thing That Runs the Entire Internet
Quick take
Your phone, the servers that sent you this page, and every supercomputer on earth run on software volunteers wrote and gave away. Here's how that happened, why it's fragile, and why it's the one industry that will let a sixteen-year-old touch real infrastructure.
Explore this topic
Article body
Open Source: The Free Thing That Runs the Entire Internet
Open the phone in your hand. Somewhere under the apps, under the settings, under everything you actually see, is a piece of software written by volunteers and given away for free. Not a trial version. Not freemium. Given away, with the instructions included.
The same is true of the servers that sent you this page, the router in your house, the ATM you used last week, and the systems that run the world's fastest supercomputers. The internet is not built on products. It is built on donations.
Almost none of the people who wrote this were paid for it. That is not a metaphor.
What "open source" actually means
Most software you use is a sealed box. You get the finished thing; you never see how it works, you cannot change it, and if it breaks you wait for someone else to fix it.
Open source software ships with its source code — the actual human-readable instructions — public. Anyone can read it, run it, modify it, and share their modified version. That is the whole idea, and it is why the word "free" here is confusing. It refers to freedom, not price. Plenty of open source software is sold. What you cannot do is hide how it works.
The permissions are set by a licence, and the licences fall roughly into two camps:
| Permissive MIT, Apache 2.0 |
Do almost anything, including using it in closed commercial products. Just keep the copyright notice. |
| Copyleft GPL, AGPL |
Do anything — but if you distribute something built on it, that has to be open too. Freedom that propagates. |
Choosing between these is a genuine philosophical argument that people have been having, loudly, for thirty years.
The stuff you are already using
Linux started as a university side project. It now runs the majority of the world's web servers, and the operating system on the top supercomputers on earth is Linux, all of them. Android is built on the Linux kernel, which means most phones in India are running a descendant of that side project.
Then there is the layer below even that — small utilities nobody has heard of that quietly sit inside almost everything. Tools for transferring data over a network, for compressing files, for handling encryption. They are in cars, televisions, printers, medical devices and game consoles. Their maintainers are often a handful of people. Sometimes one.
Your browser is open source or built on an open source engine. So is the language your favourite app was probably written in. So is most of the machine learning stack that every AI company on earth depends on. Strip out the freely donated software and the modern internet does not slow down — it stops.
Which is also the terrifying part
There is a famous cartoon that engineers send each other whenever something breaks badly. It shows a towering, precarious structure labelled "all modern digital infrastructure", balanced on a single tiny block at the bottom — described as a project some person in Nebraska has been thanklessly maintaining since 2003.
It is funny because it is documentation.
2014: a bug called Heartbleed was found in the encryption library that secured a huge share of the web. The project behind it was chronically underfunded and maintained by a tiny team.
December 2021: a flaw in Log4j — a Java logging tool almost nobody outside programming had heard of — set off a global emergency. It was in enterprise software everywhere. It was maintained by a small group of volunteers.
March 2024: a backdoor was found planted in a compression utility used across Linux systems. It had been inserted over years by someone who patiently gained the trust of an exhausted, unpaid maintainer. It was caught almost by accident, by one engineer who noticed a login was running a fraction of a second slower than it should.
The pattern is the same each time. Critical infrastructure, enormous companies depending on it, and a maintenance budget of roughly nothing. Trillion-dollar businesses were built on top of software they never paid a rupee for and never checked on.
This is slowly changing — there are now funds, sponsorship platforms and corporate programmes paying maintainers — but "slowly" is doing real work in that sentence.
A surprising amount of the internet has exactly one person responsible for it, and they are tired.
Why anyone does it
The obvious question: why write something valuable and give it away?
Some of it is genuine belief — that infrastructure this important should not be owned, and that anyone should be able to see what software is doing to them. Some of it is practical: many maintainers are paid employees at companies that need the tool to exist, so their employer funds the work. Some of it is scratching a personal itch that turned out to be everyone's itch.
And a large amount of it is reputation. In this industry, a public record of your work is worth more than a paragraph claiming you are good at things. Every commit you make is timestamped, attributed and permanently visible. People have been hired off a contribution history alone, which is not something you can say about most fields.
What this means for you, specifically
Here is the part that is unusual about open source, and worth sitting with for a second.
You cannot walk into an aerospace company at sixteen and work on a real aircraft. You cannot practise surgery. You cannot audit a bank. But you can — today, from a bedroom in any city in India — improve software that runs on millions of machines, and if the change is good, it gets accepted. Nobody will ask your age. They will ask whether the code is correct.
That is a genuinely strange and rare door, and most people never walk through it because the first step looks harder than it is.
The honest first-contribution path
- Start with something you actually use. A library from a class project, a tool you like. Not "a famous repo" — familiarity is the whole advantage.
- Read CONTRIBUTING.md first. Nearly every project has one. It tells you how they want changes submitted. Skipping it is the number one reason first contributions get closed.
- Your first contribution should probably not be code. Fix documentation that confused you. Write a clearer error message. Add a missing example. Maintainers value this more than beginners expect.
- Look for the "good first issue" label. It exists specifically so newcomers can find work that has been deliberately scoped small.
- Reproduce a bug properly. A well-written bug report with exact steps is a real contribution, and many people cannot write one.
- Expect slow replies. The person reading your submission is doing it unpaid, at night, after their actual job. Two weeks of silence is normal, not rejection.
And one thing not to do: do not submit a pile of trivial changes to inflate a contribution count. Communities have been flooded with that during badge-hunting events and they can spot it instantly. A single thoughtful fix is worth more than fifty cosmetic ones, and the wrong reputation is harder to shake than no reputation.
The first accepted change is usually three lines of documentation. That still counts.
A note on the programmes people will tell you about
Someone will mention Google Summer of Code. It is real and it is excellent — a paid programme where contributors work on open source projects with mentors.
It also requires you to be at least 18 at the time of registration. So if you are in Class 11, it is not a thing you can apply to yet. That is not a reason to wait, though; it is a reason to arrive with a contribution history already built, because that is exactly what those applications are judged on. The people who get in are almost never applying cold.
Be equally careful with the other direction — paid "open source bootcamps" promising to get you contributions. The entire ecosystem is free, public and documented. Nobody needs to sell you access to it.
The thing worth taking from this
The most valuable infrastructure humanity has built in the last forty years was mostly assembled by people who were not paid to do it, for reasons that had nothing to do with money, and then given to everyone including the companies that got rich from it.
That is either the most naive thing our species has ever done or the most impressive, and the honest answer is probably both. But it is also an open invitation, still standing, still unguarded. The code is public. The issues are public. The discussion is public.
Nobody is going to check whether you were invited.
Go find one confusing sentence.
Pick a tool you have used, open its documentation, and find one line that confused you when you were learning it. Fixing that line is a real contribution to real infrastructure, and you can do it this week.
TeenIcon courses end with something real — a shipped change, not a certificate.Comments 0
Keep reading
Similar blogs by topic
AI Agents Explained: The Tech That Will Do Your Homework and Your Job
A chatbot answers. An agent does. That one difference is quietly rewriting which jobs will exist by the time you finish college — and you can build one yourself this weekend for zero rupees.
I Asked ChatGPT to Do My Internship Search. Here's What It Got Wrong.
It gave me five perfect-sounding internships in ten seconds. Three didn't exist. Here's what AI is actually good for in a job search, and the one part it cannot do for you.
Goku Isn't Talented. That's the Whole Point.
Goku loses constantly, and every time the show cuts to him training. We remember the Super Saiyan moment and delete the montage that earned it — and we do the exact same thing to ourselves.