Somewhere along the way, “open source vs proprietary” became a tribal war — free-software idealists on one side, “you get what you pay for” pragmatists on the other. Both tribes are annoying, and both are sometimes right. If you just want to choose good software for yourself or a small team, here’s the ideology-free version.
The actual difference
Open source software publishes its source code — the recipe — for anyone to inspect, modify, and redistribute. Linux, Firefox, VLC, LibreOffice, Blender, and Android’s core are famous examples. Proprietary software keeps the recipe secret; you license the finished dish. Windows, Photoshop, and most commercial apps live here.
Note what the difference is not: open source isn’t always free of charge (companies sell support and hosted versions), and proprietary isn’t always paid (plenty of free proprietary apps exist — they just don’t show you the code, and often you’re the product).
Security: the surprising nuance
The intuitive take — “secret code must be safer, since hackers can’t read it” — turns out mostly backwards. Security through obscurity is weak protection; attackers reverse-engineer proprietary software constantly. Open source’s transparency means thousands of independent eyes can find and fix flaws, and its bugs can’t be quietly hidden.
But here’s the honest asterisk: “can be audited” isn’t “has been audited.” Major open source projects (Linux, Firefox) receive enormous scrutiny; a tiny abandoned utility on the internet’s back shelf receives none, and supply-chain attacks on small packages are a genuine modern problem. Meanwhile, big proprietary vendors employ serious security teams.
The real security question isn’t the license — it’s how actively maintained and widely scrutinized the specific software is. A thriving project of either kind beats an abandoned project of either kind, every time.
Privacy: open source’s cleanest win
Proprietary software’s business model frequently involves telemetry, data collection, and advertising — and you can’t verify what it phones home. With open source, data collection is visible in the code, and the community reacts loudly to overreach. If privacy ranks high for you, this category tilts decisively open.
Cost, and the hidden kind
Open source usually wins on price tag — but count total cost honestly. Proprietary software often buys you polish, onboarding, and a support line; open source sometimes costs your time instead: rougher edges, community forums instead of help desks, occasional DIY fixes. For a business, an employee-hour spent wrestling software is not free. Sometimes paying is the frugal choice; sometimes it’s the lazy one. Know which.
Support and longevity
Proprietary: professional support while the company thrives — but if it kills the product or hikes the subscription, you’re stranded, and your files may be locked in closed formats. Open source: no one owes you help, but no one can take the software away either — popular projects outlive companies, and open file formats mean your data stays yours. For anything you’ll rely on for a decade (archives, records, core workflows), that permanence deserves real weight.
A practical decision framework
Ask four questions: Is my data sensitive? (tilts open source, or at minimum audited vendors). Do I need guaranteed hand-holding support? (tilts proprietary or paid open source support). Will I depend on this for many years? (tilts open formats and open source). Is this category one where polish hugely matters to me daily? (judge per app — sometimes the proprietary UX is worth it, and that’s allowed).
The unsurprising conclusion
The healthiest setup for most people is a deliberate mix: open source for infrastructure, privacy-sensitive tools, and anything long-term (browser, password manager, media player, office suite); proprietary where its polish or ecosystem earns the money honestly. Choose per tool, on maintenance, privacy, and fit — not per ideology. The software doesn’t care which tribe you’re in, and neither should your toolkit.