<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Blog on libcom.de</title>
		<link>https://www.libcom.de/en/blog/</link>
		<description>Recent content in Blog on libcom.de</description>
		<generator>Hugo</generator>
		<language>en-GB</language>
		
		
		
		
			<lastBuildDate>Wed, 22 Jul 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.libcom.de/en/blog/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Immich and the question nobody asks: why open source must finally be paid for</title>
				<link>https://www.libcom.de/en/blog/immich-open-source-funding/</link>
				<pubDate>Wed, 22 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://www.libcom.de/en/blog/immich-open-source-funding/</guid>
				<description>&lt;p&gt;There is software you discover. And there is software you never let go of.&lt;/p&gt;&#xA;&lt;p&gt;Immich belongs to the second category. An open source photo and video service that does what Google Photos or Apple iCloud do — except you remain the owner. Your own pictures. Your own data. Your own infrastructure.&lt;/p&gt;&#xA;&lt;p&gt;Anyone who has looked at Immich once knows: it is good. Very good. Modern, fast, well thought out. And it is free.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Open Source is not an ideology — it is infrastructure</title>
				<link>https://www.libcom.de/en/blog/open-source-is-infrastructure/</link>
				<pubDate>Tue, 15 Jul 2025 00:00:00 +0000</pubDate>
				<guid>https://www.libcom.de/en/blog/open-source-is-infrastructure/</guid>
				<description>&lt;p&gt;There is a conversation I have over and over again.&lt;/p&gt;&#xA;&lt;p&gt;Someone asks whether we also work with &amp;ldquo;real software&amp;rdquo; — meaning proprietary products from major vendors. The question always carries the same subtext: open source is for tinkerers, idealists, people with lots of time and little money.&lt;/p&gt;&#xA;&lt;p&gt;I disagree, politely. And then I explain what is actually happening.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-misconception-about-quality&#34;&gt;The misconception about quality&lt;/h2&gt;&#xA;&lt;p&gt;The most common misconception is that quality and openness are mutually exclusive. Those who pay get better software. Those who get it for free get less.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Vendor Lock-in: When your IT works for someone else</title>
				<link>https://www.libcom.de/en/blog/vendor-lockin/</link>
				<pubDate>Mon, 02 Jun 2025 00:00:00 +0000</pubDate>
				<guid>https://www.libcom.de/en/blog/vendor-lockin/</guid>
				<description>&lt;p&gt;Vendor lock-in rarely begins with a conscious decision.&lt;/p&gt;&#xA;&lt;p&gt;Usually it begins with a nice offer. Free trial. Easy migration. Everything from one source. And two years later you discover: switching would take months, cost a fortune, and overwhelm the entire team.&lt;/p&gt;&#xA;&lt;p&gt;That is not an accident. That is the product.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-lock-in-actually-means&#34;&gt;What lock-in actually means&lt;/h2&gt;&#xA;&lt;p&gt;Technical vendor lock-in means your IT infrastructure is so closely tailored to the tools and services of a single vendor that switching becomes unrealistically expensive or complex.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
