"There's a universal dedicated storage mechanism for the state of the operating system and its related packages similar to a SQL database."
It really annoys me how ad-hoc state and values are treated in an operating system with ASCII config files.
You can always have means of human-friendliness even if the underlying data is more strictly structured such as in a database but you can't go the other way around.
Imagine almost like a SQL-like language to provision/configure/restore an operating system.
SELECT name FROM installed_packages WHERE installed_date > '2016-01-01 00:00:00';
BEGIN;
DROP FROM installed_packages WHERE package_name = "python2";
INSTALL PACKAGE WHERE package_name = "python3";
COMMIT;
Operating systems are still stuck with an over-zealous "the unix way or the highway" mentality of cobbling together fragile ad-hoc config files with arbitrary config languages.
Each package invents their own config language and forces it down your throat.
"There's a universal dedicated storage mechanism for the state of the operating system and its related packages similar to a SQL database."
It really annoys me how ad-hoc state and values are treated in an operating system with ASCII config files.
You can always have means of human-friendliness even if the underlying data is more strictly structured such as in a database but you can't go the other way around.
Imagine almost like a SQL-like language to provision/configure/restore an operating system.
Operating systems are still stuck with an over-zealous "the unix way or the highway" mentality of cobbling together fragile ad-hoc config files with arbitrary config languages.Each package invents their own config language and forces it down your throat.