Karl Voit :emacs: :orgmode:<p><span class="h-card" translate="no"><a href="https://narrativ.es/@janl" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>janl</span></a></span> The purpose is to warn bystanders to invest in technological <a href="https://graz.social/tags/complexity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>complexity</span></a> that seems to be very attractive for its advanced features without acknowledging the risks or efforts associated.</p><p>Its learning curve doesn't even allow for an easy start.</p><p>As with so many awesome tools, this is something for specific experts and not for new/occasional/advanced users.</p><p>BTDT and I've had my fair share of bad experiences.</p><p>Current pain in my setup: <a href="https://graz.social/tags/NixOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NixOS</span></a>. Instead of providing an abstraction layer to keep away certain OS setup & maintenance problems for good, I got into so many little & bigger troubles that I try to tell people only to use it when they are ready to invest its required learning effort all the way.</p><p>From my point of view, this also holds true for "advanced" file systems like <a href="https://graz.social/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ZFS</span></a>, <a href="https://graz.social/tags/XFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XFS</span></a>, ... YMMV.</p><p><a href="https://graz.social/tags/PIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PIM</span></a> <a href="https://graz.social/tags/technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>technology</span></a> <a href="https://graz.social/tags/nix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nix</span></a></p>