4 ms·
I get that people enjoy very minimalist computer experiences, but startup time is hardly that different between these programs and other slightly more ergonomic
by Macha 6y ago
I get that people enjoy very minimalist computer experiences, but startup time is hardly that different between these programs and other slightly more ergonomic programs which offer conveniences like a config file.
If you look at my startup time for my system it goes something like this:
10s - waiting for monitor to wake up to pick OS at dual boot menu
15s - typing disk encryption password
15s - system uses disk encryption password to retrieve LUKS key
5s - Literally the entirety of my OS and window manager and autostart programs beginning.
I use i3 for my window manager, which manages to launch instantly, and alt-enter launches alacritty for my terminal, which also launches instantly. But even heavier terminals like xfce4-terminal launch very quickly. These programs are lightweight sure, but they don't need to be recompiled for configuration and have some ergonomics. I don't see the marginal benefit of maybe 4s at boot time being worth that hassle.
- tutfbhuf 6y agoI completely agree. Suckless tools shouldn't be pedantic about C code minimalism. As per my definition, suckless tools are lightweight, KISS and offer some simple ergonomics. I find it nice to be able to scroll the terminal up, when I'm not inside of tmux.
- tarkin2 6y agoThe main thing I loved about suckless and missed on OS X was DWM. Dealing with windows, even with the tiling aspects, hammerspoon to automate things, and playing around with configs to turn off all the animation, on OS X I was still much more productive using DWM.
- xiwenc 6y agoStronger yet I rarely reboot my systems. Either they run 24/7 or I put them to sleep. There’s definitely good use for these optimized tools. Especially on old systems with low resources and slow CPU’s. I generally like the simplicity of suckless tools. dmenu together with i3 is a nice duo.
- dhimes 6y agoYou have working sleep? Man I'm so jealous.
- ssb1 6y agoI've had working sleep since at least 2010 on ThinkPads and Dell XPS, Ubuntu and now Mint.
- dhimes 6y agoGeez. I think my Mint worked for a while. Now Win10 doesn't even work. I have to reboot always- I suspect it's because of my second monitor (I only started using it as a real work machine since the WFH started).
- nsajko 6y ago> You have working sleep? Man I'm so jealous. Suspend to RAM does not work for you?! What distro do you use and what kernel? What do the files /sys/power/state and /sys/power/mem_sleep contain? Maybe it's just a SystemD issue?
- SkySkimmer 6y agoI'm someone else but I get https://gitlab.freedesktop.org/drm/amd/-/issues/883 https://gitlab.freedesktop.org/drm/amd/-/issues/883 on a T495s with debian testing
- nsajko 6y agoI'm sad and surprised that one still has to go through so much trouble trying to use an AMD computer with Linux, especially considering the performance and security situation with Intel in the last couple of years. For what it's worth, a comment [0] on the Archlinux BBS says that Linux 5.6.13 fixed the issue for the user's t495 and Debian seems to have 5.6.14, so if you haven't yet tried updating the kernel, definitely try now. [0] https://bbs.archlinux.org/viewtopic.php?pid=1905479#p1905479 https://bbs.archlinux.org/viewtopic.php?pid=1905479#p1905479
- simias 6y agoI don't see why you're focusing on speed (does the author even mention it? I skimmed TFA and didn't find it mentioned). Less bloat, simpler code means fewer bugs and it means that it's easy for a hacker/power user to dig into the code to understand and modify it, that's the killer feature. After one hour poking into DWM I understood how it worked and how I could modify it to fit my needs exactly. I use a bunch of suckless tools, in particular DMW. I don't necessarily agree with all their choices but for me it's about configurability and reliability. I consider myself a power user, I know how things work, I don't need a gui to configure my keyboard or network interface. I don't want daemons running in the background and overwriting the settings I apply manually with the command line (a common issue I have with more fully fledged "desktop environments"). Ergonomics easily win too, sure I have to mess with C code to get the config I want, but then it's basically tailor-made vs. ready-made. All the functions I use the most are one key keystroke away, I use the mouse so little that I often find myself searching for it because it ended up buried underneath some papers. I want to focus the terminal? Win-C. I want to focus Vim? Win-E. Firefox? Win-w. I have special customization to sticky windows the way I like, placement rules etc... Everything is fast, reliable, no pointless transitions, no cruft, no having to worry about the next update changing a behaviour that I use and me having to figure out how to revert the change or relearn how I do things. >I don't see the marginal benefit of maybe 4s at boot time being worth that hassle. Before I used DWM I used StumpWM for more than a decade, an other tiling WM. Being written in Common Lisp it was quite slow to boot up from an image dump (especially 10+ years ago on HDDs and vastly less powerful CPUs). For me performance is highly irrelevant, the "hassle" is what I'm in it for. It's like learning to touchtype, at first it's immensely frustrating but once you're past the learning curve it gets really beneficial. Digging throw DWM's code is harder than clicking on Gnome's menus, but once you've got it working exactly like you want you probably won't have to touch it for a long while. The last significant change I made to my DWM fork dates from July 27 2018. Since then I've only tweaked a couple of keybindings.
- jck 6y agoDoesn't everything you're saying also apply to most tiling window managers? i3, bspwm etc
- deleted 6y ago[deleted]
- fish45 6y agoI don't care about startup time in my window manager but st launches in 50 ms and alacritty takes 500 which is a noticeable and annoying difference so I'll take st every time. A lot of the time I want to open the terminal with a specific command in mind so with alacritty I ended up typing before it launched.