Tons of fun once you get past the first week of misery in switching. Full support here. :)

I personally use Engrammer. This being said I know the symbol locations can be a shock, thus the other recommendations too. :)

FYI there are much better layouts than even Dvorak.

During Covid a ton of work was done on key layouts. Whole new statistical analysis tools were written from scratch. If you are looking for a new key layout I would focus on post Covid ones.

Personally I like Graphite, Gallium, and Engrammer.

https://github.com/rdavison/graphite-layout

https://github.com/GalileoBlues/Gallium

https://github.com/sunaku/engrammer

They’re trying to exploit what they consider a loophole in the AGPL to stop people from forking the project.

At the same time they refuse to accept any PRs.

FSF has a great write up about it.

https://www.fsf.org/blogs/licensing/agpl-is-not-a-tool-for-taking-freedom-away

Strong disagree. China is a reliable if not self interested partner.

The US goes from selling you weapons to threatening to invade you randomly at the flip of narcissistic coin.

Ipv8 isn’t a real proposal being taken seriously by anyone just fyi. The original white paper was AI slop with full on hallucinated sources.

A few issues here.

It’s very rapidly taking over the Linux ecosystem, limiting freedom to choose another init system.

Nobody working with Linux professionally in 2026 would say this. Systemd has taken over and has been the defacto choice for a LONG TIME. The last production grade Linux to not use Systemd was rhel 6. Rhel 6 was released in 2010 and full support ended in 2016.

Also no companies are using Alpine for “lack of systemd” Companies aren’t installing alpine Linux on bare metal outside of embedded devices. The appeal of Alpine Linux is containerization or embedded. Alpine Linux lets you release 20mb container images compared to 200mb for even slim Debian images. This is a great thing. But not related to systemd.

If we look at what professionals working with Linux use on bare metal or even on non ephemeral cloud hosts we find RHEL / OEL / Rocky / Alma, Ubuntu LTS, Suse Enterprise, Amazon Linux, Azure Linux, and rarely Debian.

Yes there are outliers but antivax doctors are outliers too.

I do agree that in this thread you do are pressing into the “not anti” image. This being said that was not the case prior to this thread.

Also there is no systemd “monopoly”. Systemd was chosen by volunteers at community centric distros like Arch and Debian, as well as by more corp distros like Redhat or Ubuntu.

Those distro maintainers (volunteers and paid) looked at all the options and chose what they thought was best.

Those maintainers also chose not to support alternative startup systems for the same reason why VW does not offer alternative chassis options on the VW Golf. (In this example the engine would be the kernel)

Aka the maintainers don’t want to massively increase the workload they would need to do. Volunteer community distros only have a limited amount of resources and choose to allocate them how they will.

Corpo distros just are being corps and want to save money.

Using the term “monopoly” in this context dismisses the Linux community’s choice as developers and contributors. The Linux community is unique in that we are both the producers and consumers of the community project.

I would recommend reading this mailing list announcement thread to get a better understanding. The Linux from scratch dev team explains why they went from offering a choice to a “monopoly”. https://lists.linuxfromscratch.org/sympa/arc/lfs-announce/2026-02/msg00000.html

Edit: The announcement is wrong in that KDE in fact does not require systemd.

No?? In the past you were saying weirdly anti systemd stuff. So much so that I went out of my way to tag you.

More like “this person rants so much against basketball that it’s weird”

To any new Linux users, this is a good example of Linux “antivax” mindset.

Actual Linux admins, people who use Linux at scale, people who design things and use Linux to do things disagree.

There is a reason why Redhat, Debian, Ubuntu, and Arch all ship with and recommend systemd as the startup system. ALL as in 100% of large Linux deployments on bare metal use systemd.

If you want to play with startup systems that’s fine there are obscure distros out there for you. Startup system swapping can be a fun hobby.

But don’t be tricked by the very loud but very small Linux “antivaxers” group.

But there is something weird about comparing any start up system to cancer. It was weird when Balmer compared Linux to cancer. It was weird then and it’s weird now.

As someone else in the thread said „Rent Free“. It’s true.

Perfect example. This person has systemd so much on the brain I actually tagged them as weirdly against systemd some time ago. lol

Exactly. A very small but VERY disproportionally loud group.

They uninstalled systemd from their computers and installed it on their brains.

Big fan of Helix. Best part is that it dose not need any plugins to be a modern editor. Just configure any LSPs you want and it all just works including things like fuzzy finding, multiple cursors, file browsing etc.

I use it daily and think so. Best part is that it dose not need any plugins to be a modern editor. Just configure any LSPs you want and it all just works including things like fuzzy finding, multiple cursors, file browsing etc.

This all being said a plugin system is close to being added. :)

😂

You’re allowed to not fiddle with it.

I can see how for some people cron is more straightforward to learn, at least till you need to handle logging, checking for cron results, handling when the triggered event can’t happen that instance, ensuring only one instance of the triggered thing happens at once, adding time jitter, etc.

Then timers are way simpler. Timers let you create robust timed events for free. With cron you need to do all that yourself.

Weird for sure. Why do you keep on asking this question in different ways on different accounts? Are you trying to justify it? Is it a fetish?

Inquiring minds want to know!

That’s because you know cron. If you knew timers equally as well they would be easier. And they let you handle the edge cases (retry, randomness, tracking, logs etc) without the need for a custom script.

Once you factor in the production edge cases I think timers are clearly easier. You get all of it for free.