Now my arch is bloated more than the default ubuntu
Now my arch is bloated more than the default ubuntu
This is the way.
Install tiling wm, because I canāt without anymore. I stall a DE, because I actually like the discoverability of graphical settings programs.
Is it unmaintained completely or just feature complete and not getting recent updates?
Iāve seen people say āthis tool isnāt being maintained because there arenāt recent check insā and those two things are very different.
It is written in Bash which I guess makes it pretty high level and stable. Until it breaks it shouldnt need much work.
Bash is damn slow though, so fastfetch (mainly in C) is way better for the āarch flexā
Flatpaks have helped me a lot reducing bloat, avoiding dependency hell.
That said, probably there's some overlapping dependencies that, if installed in a different way I could save some space, but it's not worth it in my opinion.
I'm also using rootless podman+systemd for certain services, but that's been a mixed bag compared with plain old docker or LXC.
Flatpak is like the most bloated thing ever because of the runtime and all the dependencies it needs.
I did a test, flatpak with just firefox installed used 3 GiB of space.
While 15 appimages that includes heavy applications like libreoffice, kdenlive and two web browsers uses 1.2GiB.
Started playing with arch this week for the first time. Got a pretty good laugh when I realized that I forgot to install a dhcp client and had to boot the install media again to add networking.
I appreciate what theyāre doing and Iām going to keep poking at it, but my first impression is that philosophy is driving and the utility is in the back seat.
It seems to be seen across all platforms.
What I find interesting is that no one is asking about the quality of code, nor do they seem concerned about the dependencies but they do care about that one package/app/program of any size they see and donāt immediately know why itās there.
I remember what my idea of making backups was when I was a wee grasshopper.
Making a backup of the whole OS instead of just the configs and user files.
I have come a long way since then.
Thatās committing the cardinal sin of cherrypicking your backup contents. You may end up forgetting to include things that you didnāt know you needed until restore time and youāre creating a backup that is cumbersome to restore. Always remember: you should really be creating a restore strategy rather than a backup strategy.
As a general rule I always backup the filesystem wholesale, optionally exclude things of which Iām 100% sure that I donāt need it, and keep multiple copies (daylies and monthlies going some time back) so I always have a complete reference of what my system looked like at a particular point in time, and if push comes to shove I can always revert to a previous state by wiping the filesystem and copying one of the backups to it.