Really good read, thanks for posting this! Not sure I’m personally ready to make the dive yet… as I dev I totally see the value of an immutable base system, but yet I can’t see the overhead (e.g....
Really good read, thanks for posting this!
Not sure I’m personally ready to make the dive yet… as I dev I totally see the value of an immutable base system, but yet I can’t see the overhead (e.g. “how do I expose this USB device/network directory to this application again?”) being worth the benefits, at least with current tooling and for my personal usage patterns.
The security of sandboxing really, really appeals to me… and I think it’d be a great asset if the rest of the average corporate environment were up to snuff, but that’s probably at least a decade away. From a UX perspective, I’d want an OS with a built-in GUI capable of listing packages and editing all permissions on the fly before making the leap. I’ll skip out on the manual nix configs and trying to remember command-line incantations for yet another set of arcane, soon-to-be-obseleted tools, TYVM.
Really good read, thanks for posting this!
Not sure I’m personally ready to make the dive yet… as I dev I totally see the value of an immutable base system, but yet I can’t see the overhead (e.g. “how do I expose this USB device/network directory to this application again?”) being worth the benefits, at least with current tooling and for my personal usage patterns.
The security of sandboxing really, really appeals to me… and I think it’d be a great asset if the rest of the average corporate environment were up to snuff, but that’s probably at least a decade away. From a UX perspective, I’d want an OS with a built-in GUI capable of listing packages and editing all permissions on the fly before making the leap. I’ll skip out on the manual nix configs and trying to remember command-line incantations for yet another set of arcane, soon-to-be-obseleted tools, TYVM.