What is open source and why it matters to me

Open source is one of those terms that gets used so often it loses meaning. "We are open source" has become a marketing phrase. But the core idea is simple and genuinely important: the source code is available for anyone to read, modify, and distribute.

Why it matters practically

You can see what the software does. When I use Vaultwarden for my passwords, I can read the source code and verify it handles encryption correctly. When I use a proprietary password manager, I am trusting their marketing claims.

It does not disappear. When a company shuts down or gets acquired, proprietary software dies with it. Open-source software can be forked and maintained by the community. Nextcloud exists because ownCloud's founder disagreed with the company's direction and forked the project. The software survived.

No vendor lock-in. If I do not like where a project is heading, I can fork it, switch to an alternative, or contribute a fix. With proprietary software, my only option is to leave and start over.

Free as in freedom, not just free as in beer. Many open-source tools are free to use, but the important freedom is the ability to modify them. I have patched bugs in tools I use, submitted fixes upstream, and customized software to fit my workflow. You cannot do that with proprietary code.

How it shapes my choices

When I pick tools for my development stack or homelab, open source is a strong preference but not an absolute requirement. Here is how I think about it:

Default to open source when a good option exists. For most developer tools, there is an open-source option that is as good or better than the proprietary alternative. Docker, PostgreSQL, Caddy, Nextcloud, Git. These are not compromises. They are best-in-class.

Use proprietary when it is genuinely better for the specific task. I use Vivaldi as my browser because it has features no open-source browser matches for my workflow. The core rendering engine (Chromium) is open source, even if the UI layer is not.

Self-host when practical. Running open-source software on my own hardware gives me the full benefit: I control the data, the updates, and the configuration. This is why I run Nextcloud instead of using Google Drive, even though Google Drive has a smoother experience.

Contributing back

Using open source without contributing back is fine. Not everyone has time or skills to contribute code. But there are other ways:

• Report bugs with clear reproduction steps
• Write documentation or improve existing docs
• Answer questions in forums or issue trackers
• Donate to projects you depend on
• Share open-source tools you find useful

I have contributed small fixes to a few projects I use. Nothing groundbreaking, but each contribution made the tool slightly better for everyone. That feedback loop is what makes open source work.

The honest downsides

Open-source software sometimes has rougher edges. The UX might not be as polished. Documentation can be inconsistent. Support means reading GitHub issues instead of chatting with a support team.

For critical business tools where downtime costs real money, paying for software with a support contract can be worth it. Open source and proprietary are not mutually exclusive either. Many open-source projects offer paid support, hosted versions, or enterprise features.

The bottom line

Open source is not just a licensing model. It is a philosophy about transparency, ownership, and community that aligns with how I think about technology. I want to understand the tools I use, control the services I depend on, and contribute to the ecosystem that makes all of this possible.

Sources

• Open Source Initiative
• Choose a License