|
|
|
|
|
|
by ekianjo
971 days ago
|
|
|
> This idea has been successfully used by likes of android chromeOS and such to create seamless and risk free updates. Those are not updates, they are just containers deployments at the end of the day (Flatpak and all related technologies). > your normal distro does updates by pulling every package on your system and swapping files mid running this can cause miriad of issues just by doing it and another miriad if update is stopped mid updating(not always but sometimes). So this means your system is being recomposed at runtime In practice rolling distros so that every day, with very little issues. (Arch is a good example of that). |
|
|
well my experiance and experiance of many other people say otherwise and most wide reaching example look at how a single miss configured package(dependancy misconfiguration) deleted Linus Sebastians pop desktop.(and no the fact that he didnt read doesnt excuse poor package dependancies that even got to that point) that could have easily been caught if composition didnt happen at runtime
On non 0 number of occasions i lost or recoverably broke arch installs while it was updating using pacman just because X or DE's WM got crashed during update because of update. just 2 examples out of many for why composition at runtime is a bad idea for linux to be a more mainstream OS