Skip Navigation
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)AI
7ai @sh.itjust.works
Posts 3
Comments 13

Buddha explaining the oneness of all sentient beings

3

The five wake up calls to stop clinging and taking action mindfully

7
Why do so many mobile versions of sites run worse on phone than desktop versions?
  • Because modern web is bloatware. Too much javascript, CSS, ads and cookie popups. A phone's hardware and internet speeds are generally not as fast as a desktop. So, it takes much longer to render on a phone.

    Also, a lot websites nowadays deliberately make their mobile web experience shitty (cough ** reddit cough) to force their users to install their app.

  • 20gb ram, 10gb zram, 10gb swap, default values. What should I change?
  • Zram usually has a very high compression ratio - around 4:1 for lz4 and 6:1 for zstd. You can set zram to 40-50 GB. It will still use less than 1/2 of your ram.

    Zram has an option to write poorly compressible data to the disk instead of storing it in the ram. I would split the swap partition - 3 GB for zram writeback and rest for ordinary swap.

  • I switched from Nixos to void Linux. Here's my experience so far.
  • I was using flakes. I gave the reason why it's data intensive. If a core dependency like glibc is updated, it's hash will change and all packages that depend on it need to be rebuilt and rehashed. It'll download all packages again even though there's minimal change.

  • I switched from Nixos to void Linux. Here's my experience so far.
  • Nix has a great potential as a replacement for flatpak actually as it is source based. You can guarantee what you are installing is based on which source code by compiling yourself.

    Flatpak and the others are packaged by upstream. A developer can put malware in a package and upload it to flathub. That's why it needs permission management, sandboxing etc to minimize the risk.

  • I switched from Nixos to void Linux. Here's my experience so far.
  • Yeah. Most small changes will not rebuild everything. It's just the core dependency updates that are most expensive. Like say openssl got a minor update. Now every package that depends on it needs to be rebuilt and rehashed because of the way nix store works.

  • I switched from Nixos to void Linux. Here's my experience so far.
  • Yeah there's a lot of state accumulation especially in home folder which I clear manually from time to time.

    In Nixos you can configure the impermanence module to clear unwanted state on your system and make it a "fresh install" on every reboot.

  • I switched from Nixos to void Linux. Here's my experience so far.
  • You mean in terms of how fast it feels? I have never heard anyone saying this before. Can you share some details and perhaps some tips to improve performance on Nixos?

    What hardware do you run Nixos on and do you modify and rebuild a lot of packages on nixpkgs?

  • I switched from Nixos to void Linux. Here's my experience so far.
  • Arch and void are very similar except void has a smaller community and much smaller set of packages to install. Arch also has better documentation.

    Void is considered more lightweight because it uses runit instead of systemd and a choice to use musl instead of glibc.

    I feel for most, arch is a better choice of the three.

  • I switched from Nixos to void Linux. Here's my experience so far.

    I hopped from arch (2010-2019) to Nixos (2019-2023). I had my issues with it but being a functional programmer, I really liked the declarative style of configuring your OS. That was until last week. I decided to try out void Linux (musl). I'm happy with it so far.

    Why did I switch?

    1. Nix is extremely slow and data intensive (compared to xbps). I mean sometimes 100-1000x or more. I know it is not a fair comparison because nix is doing much more. Even for small tweaks or dependency / toolchain update it'll download/rebuild all packages. This would mean 3-10GB (or more) download on Nixos for something that is a few KB or MB on xbps.

    2. Everything is noticeably slower. My system used way more CPU and Ram even during idle. CPU was at 1-3% during idle and my battery life was 2 to 3.5h. Xfce idle ram usage was 1.5 GB on Nixos. On Void it's around 0.5GB. I easily get 5-7h of battery life for my normal usage. It is 10h-12h if I am reading an ebook.

    Nix disables a lot of compiler optimisations apparently for reproducibility. Maybe this is the reason?

    1. Just a lot of random bugs. Firefox would sometimes leak memory and hang. I have only 8 GB of ram. WiFi reconnecting all the time randomly. No such issues so far with void.

    2. Of course the abstractions and the language have a learning curve. It's harder for a beginner to package or do something which is not already exposed as an option. (This wasn't a big issue for me most of the time.)

    For now, I'll enjoy the speed and simplicity of void. It has less packages compared to nix but I have flatpak if needed. So far, I had to install only Android studio with it.

    My verdict is to use Nixos for servers and shared dev environments. For desktop it's probably not suitable for most.

    31