lckdscl's site

My obsession with speed (not the drug)

August 25, 2021

Updated 06/01/2022


At first, I tried to configure Neovim’s plugins using Packer as opposed to using Vim-plug. I found out that it is easier to lazy-load plugins, so I tried to lazy-load as many as I can. Right now, I have 38 41 44 plugins, and so far only two of them are not lazy-loaded, as doing so messed things up no matter what I tried. By doing #!bash nvim --startuptime /path/to/file, it is reported that my Neovim takes 71 64 ms to load the screen, pretty good considering I have a lot of plugins.


I removed miniconda because it was taking a while to load; I wasn’t bothered about autoloading it, and I might try using pyenv instead because whatever conda tried to initialise in my zshrc takes up 60 ms. I removed those lines added by conda and when doing time zsh -i -c exit, I only see a total of 20 ms now. Pretty magical, I’m also not using any bloated zsh configuration like oh-my-zsh, because I used to, and it added a plethora of aliases I never use and get confused by. I took my time to configure my zshrc properly, and now it feels much faster! Instead of using compinit, I’m now using fzf instead, my setup includes fzf fuzzy searching + syntax-highlighting + auto-suggest + zoxide as an autojump replacement. I can tell you that my shell feels pretty and powerful.


I moved to systemd-networkd on my desktop because I don’t change network frequently. The two alternatives mentioned on the Arch wiki: Network Manager and dhcpcd, are unfortunately both quite slow. The result of the move makes booting up a lot faster. As a hardcore systemd fan /s, I’ve been using systemd-boot as far back as I can remember. It’s not very customisable but who the hell has the time to rice their bootloader. Folks on r/unixporn might attest to this but they should go do their work instead. Finally, a short message: say all you want about systemd, it werks.