Post #3866754

@sarahjamielewis@mastodon.social systemd's shark-jumping has now gone further with Poettering et al. forming a startup called Amutable, where the general idea appears to be promoting read-only-but-modifiable VMs/containers/whatever. Read-only is often good, but adding a general-purpose -but-modifiable bit tends to add a _ton_ of complexity of everywhere [1] and is IMO a counterproductive idea [2]. Whatever the case, now everyone gets to deal with all the related features/problems they upstream into systemd. I have been pretty ok with systemd's original scope viz. as an init system, but at this point I'd just like to throw all of it out. [1] The systemd approach appears to be largely following the pattern set by Android's APEX thing which added a ton of complexity on top of the already rather extreme complexity of AOSP. [2] Unless you do it cheap&cheerful like the OpenWRT packages-overlay thing, which is fine if not particularly conducive to security.