<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open Source on The Coders Blog</title><link>https://thecodersblog.com/categories/open-source/</link><description>Recent content in Open Source on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://thecodersblog.com/categories/open-source/index.xml" rel="self" type="application/rss+xml"/><item><title>Fisker's Open Source Bet: A Case Study in Automotive Hail Marys</title><link>https://thecodersblog.com/fiskers-open-source-bet-a-case-study-in-automotive-hail-marys/</link><pubDate>Sun, 17 May 2026 03:54:12 +0000</pubDate><guid>https://thecodersblog.com/fiskers-open-source-bet-a-case-study-in-automotive-hail-marys/</guid><description>&lt;h2 id="fiskers-open-source-bet-a-hail-mary-for-the-automakers-who-cant-pay-the-piper"&gt;Fisker&amp;rsquo;s &amp;ldquo;Open Source&amp;rdquo; Bet: A Hail Mary for the Automakers Who Can&amp;rsquo;t Pay the Piper&lt;/h2&gt;
&lt;p&gt;When a company faces the precipice of bankruptcy, its strategic decisions often morph from calculated risks into desperate gambits. Fisker Inc.&amp;rsquo;s June 2024 Chapter 11 filing, which effectively halted OTA updates and support for its ~11,000 Ocean owners, thrust the brand into a state of accelerated decay. What followed was not a corporate decree to embrace open source, but a groundswell of owner-led reverse engineering. This wasn&amp;rsquo;t a strategic move to foster community or innovate; it was an act of survival by the end-users, a stark illustration of what happens when a company outsources its product&amp;rsquo;s long-term viability without a plan for its foundational software.&lt;/p&gt;</description></item><item><title>The Hidden Cost of Community Support: When Maintainers Become Unpaid Support Staff</title><link>https://thecodersblog.com/the-hidden-cost-of-community-support-when-maintainers-become-unpaid-support-staff/</link><pubDate>Sat, 16 May 2026 07:21:56 +0000</pubDate><guid>https://thecodersblog.com/the-hidden-cost-of-community-support-when-maintainers-become-unpaid-support-staff/</guid><description>&lt;h2 id="the-unpaid-support-desk-how-open-source-infrastructure-is-draining-its-maintainers"&gt;The Unpaid Support Desk: How Open Source Infrastructure is Draining Its Maintainers&lt;/h2&gt;
&lt;p&gt;The vast majority of modern software development hinges on open-source projects. Estimates suggest 96% of companies leverage OSS, a foundation we collectively value at $8.8 trillion if we had to build it ourselves. This colossal value extraction, however, comes with an invisible, often crippling, cost borne by a small cadre of maintainers. These individuals, frequently working without compensation, find themselves not just as coders, but as unpaid support staff, community managers, and general infrastructure caretakers. This dynamic is a primary driver of burnout, threatening the very health of the projects we all depend on.&lt;/p&gt;</description></item><item><title>When 'Open' Becomes a Legal Minefield: Navigating the Complexities of OSS License Enforcement</title><link>https://thecodersblog.com/when-open-becomes-a-legal-minefield-navigating-the-complexities-of-oss-license-enforcement/</link><pubDate>Fri, 15 May 2026 17:18:12 +0000</pubDate><guid>https://thecodersblog.com/when-open-becomes-a-legal-minefield-navigating-the-complexities-of-oss-license-enforcement/</guid><description>&lt;h2 id="when-open-becomes-a-legal-minefield-navigating-the-complexities-of-oss-license-enforcement"&gt;When &amp;lsquo;Open&amp;rsquo; Becomes a Legal Minefield: Navigating the Complexities of OSS License Enforcement&lt;/h2&gt;
&lt;p&gt;The promise of open source has always been one of collaboration, shared progress, and accessible innovation. Yet, beneath the surface of this idyllic vision, a growing number of projects are finding themselves entangled in legal disputes over license violations. This isn&amp;rsquo;t about a company failing to share their modifications under a copyleft license; it&amp;rsquo;s about projects actively pursuing legal remedies for what they deem to be exploitation of their work. This trend forces us to confront uncomfortable questions about sustainability, community governance, and the very definition of &amp;ldquo;open.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Linux Gaming: Does Proton's Windows API Trickery Actually Work, or Is It Just Hype?</title><link>https://thecodersblog.com/linux-gaming-does-protons-windows-api-trickery-actually-work-or-is-it-just-hype/</link><pubDate>Thu, 14 May 2026 17:10:20 +0000</pubDate><guid>https://thecodersblog.com/linux-gaming-does-protons-windows-api-trickery-actually-work-or-is-it-just-hype/</guid><description>&lt;h2 id="linux-gaming-does-protons-windows-api-trickery-actually-work-or-is-it-just-hype"&gt;Linux Gaming: Does Proton&amp;rsquo;s Windows API Trickery Actually Work, or Is It Just Hype?&lt;/h2&gt;
&lt;p&gt;Let&amp;rsquo;s cut to the chase: you&amp;rsquo;re eyeing a Linux gaming rig and wondering if Valve&amp;rsquo;s Proton is the magic bullet it&amp;rsquo;s made out to be, or just another layer of complexity promising the moon and delivering a dimly lit nebula. The short answer? It&amp;rsquo;s complicated, and whether it &amp;ldquo;works&amp;rdquo; depends entirely on your definition and your tolerance for its inherent trade-offs. For years, the dream has been to ditch Windows entirely for gaming, but reality bites, and sometimes it bites harder on Linux.&lt;/p&gt;</description></item><item><title>Budget Code Signing Strategies for Open-Source Projects</title><link>https://thecodersblog.com/budget-code-signing-strategies-for-open-source-projects/</link><pubDate>Thu, 14 May 2026 14:12:23 +0000</pubDate><guid>https://thecodersblog.com/budget-code-signing-strategies-for-open-source-projects/</guid><description>&lt;h2 id="is-code-signing-a-luxury-only-for-big-budgets-think-again"&gt;Is Code Signing a Luxury Only for Big Budgets? Think Again.&lt;/h2&gt;
&lt;p&gt;Let&amp;rsquo;s cut to the chase. You&amp;rsquo;re building a Rust CLI tool, pushing it out to the world, and you&amp;rsquo;ve hit the &amp;ldquo;distribution&amp;rdquo; wall. Suddenly, everyone&amp;rsquo;s talking about code signing. For individuals and small open-source teams, the immediate reaction is often, &amp;ldquo;This is going to cost a fortune.&amp;rdquo; Commercial certificates, HSMs, yearly fees – it sounds like a luxury reserved for enterprise behemoths. But is it? Can you actually secure your open-source distribution without emptying your project&amp;rsquo;s (or your own) wallet? We’re going to dissect the pragmatic, often overlooked, and sometimes slightly janky, ways to sign your code when budget is tighter than a submarine’s hatch.&lt;/p&gt;</description></item><item><title>draw.io Desktop: Powerful Open-Source Diagramming</title><link>https://thecodersblog.com/draw-io-desktop-visual-diagramming-2026/</link><pubDate>Fri, 08 May 2026 15:40:16 +0000</pubDate><guid>https://thecodersblog.com/draw-io-desktop-visual-diagramming-2026/</guid><description>&lt;p&gt;&lt;strong&gt;Democratizing Visual Communication for Complex Systems&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;In the realm of software development, IT operations, and project management, clarity is king. Effectively communicating intricate architectures, workflows, and system designs can be the difference between a successful project and a tangled mess of misinterpretations. For years, professionals have grappled with a landscape dominated by expensive, proprietary diagramming tools. Then came draw.io, and its desktop iteration, draw.io Desktop (now also known as diagrams.net Desktop), has quietly carved out a significant niche as a robust, feature-rich, and remarkably accessible solution. This isn&amp;rsquo;t just another free tool; it&amp;rsquo;s a strategic asset for anyone looking to visualize complexity without breaking the bank.&lt;/p&gt;</description></item><item><title>[Open Source Licensing]: PHP License Dies, Replaced by BSD 3-Clause</title><link>https://thecodersblog.com/php-license-shift-2026/</link><pubDate>Fri, 08 May 2026 15:24:54 +0000</pubDate><guid>https://thecodersblog.com/php-license-shift-2026/</guid><description>&lt;h3 id="a-new-dawn-for-php-licensing-embracing-broader-freedoms"&gt;A New Dawn for PHP Licensing: Embracing Broader Freedoms&lt;/h3&gt;
&lt;p&gt;For years, the PHP ecosystem has operated under a unique licensing umbrella, a combination of the custom PHP License v3.01 and the Zend Engine License v2.0. While these licenses served their purpose, they carried with them a degree of complexity and, critically, a significant hurdle: incompatibility with the widely adopted GNU General Public License (GPL). This changed with the advent of PHP 9.0, ushering in a new era defined by the ubiquitous BSD 3-Clause license. This isn&amp;rsquo;t just a minor update; it&amp;rsquo;s a fundamental shift that removes legacy baggage, enhances interoperability, and positions PHP for a more integrated and permissive future within the broader open-source landscape.&lt;/p&gt;</description></item><item><title>OpenTrafficMap: Why Community-Driven Real-time Geographic Data is the Next Big Thing in 2026</title><link>https://thecodersblog.com/opentrafficmap-the-underestimated-power-of-community-driven-real-time-geographic-data-2026/</link><pubDate>Wed, 29 Apr 2026 21:29:13 +0000</pubDate><guid>https://thecodersblog.com/opentrafficmap-the-underestimated-power-of-community-driven-real-time-geographic-data-2026/</guid><description>&lt;p&gt;Proprietary traffic data isn&amp;rsquo;t just expensive; it&amp;rsquo;s an opaque black box dictating critical urban decisions, leaving city planners and developers blind to its inner workings and ripe for vendor lock-in. This era of closed data, controlled by a handful of corporations, is rapidly drawing to a close. The future of urban mobility and smart city infrastructure hinges on &lt;strong&gt;OpenTrafficMap&lt;/strong&gt;: a transparent, community-driven approach to real-time geographic data that is poised to fundamentally redefine how we understand and interact with our cities by &lt;strong&gt;2026&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Public Code Is No Longer Optional: The Netherlands’ Bold Bet on Open Source Sovereignty</title><link>https://thecodersblog.com/the-netherlands-self-hosted-government-open-source-code-platform-2026/</link><pubDate>Wed, 29 Apr 2026 10:27:43 +0000</pubDate><guid>https://thecodersblog.com/the-netherlands-self-hosted-government-open-source-code-platform-2026/</guid><description>&lt;p&gt;Governments worldwide face an ultimatum: either embrace transparent, open-source public code for critical infrastructure, or continue to erode digital sovereignty and citizen trust through opaque, proprietary systems.&lt;/p&gt;
&lt;h2 id="the-digital-sovereignty-imperative-why-public-code-is-no-longer-optional"&gt;The Digital Sovereignty Imperative: Why Public Code is No Longer Optional&lt;/h2&gt;
&lt;p&gt;The era of governments ceding control over their core digital infrastructure to private vendors must end. Proprietary systems have fostered &lt;strong&gt;vendor lock-in&lt;/strong&gt;, creating deeply entrenched economic dependencies that strangle agility and innovation for public services. These dependencies aren&amp;rsquo;t just about cost; they’re about control. Public bodies find themselves unable to adapt, unable to innovate, and ultimately, unable to serve citizens effectively without the explicit permission and costly intervention of external corporations.&lt;/p&gt;</description></item></channel></rss>