

Totally fair and exactly part of my original disdain. I was happy with SysV and Upstart. But here we are and I’ve got things to do. ;)
I hated repackaging all my software for systemd. lol. We waited as long as we could before eating that pie.
Totally fair and exactly part of my original disdain. I was happy with SysV and Upstart. But here we are and I’ve got things to do. ;)
I hated repackaging all my software for systemd. lol. We waited as long as we could before eating that pie.
It was highly contentious for a number of years - largely because it had a lot more functionality and touched more parts of the OS than the init systems it was designed to replace. It was seen as overzealous by the naysayers.
I was in the never system-d camp for a long time because I felt like my ability to choose was being removed. Even some distros that provided alternate init systems eventually went systemd-only.
But I’ve come around - it’s fine, good even - though ultimately I had no choice or say in it.
It’s very straightforward and easy to write one’s own units. It’s reasonably easy to debug and often helpful when something isn’t working as expected.
Like all things in the world of software, many folks are going to try (and eventually succeed) to make a better mousetrap.
This particular init system’s design goals seem (at least to me) to indicate a focus on small, embedded and/or more secure systems where the breadth of tools like systemd are a hindrance.
I really appreciate your response. It’s incredibly helpful and deeply thoughtful. Thank you.
What comes next is not directed at you but rather provides some other color based on a few things you touched on.
I worked for the guy. He gets no slack from me. He changed my life in many ways both wonderful and not. And while it’s unlikely I’d work with or for him again he was a net positive in my life.
I don’t see product the way he sees product which is exactly as you note: it’s for him. Some of that “for him” approach has resonated deeply with the OSS community and still does. He changed Cloud Computing in the best of ways. He’s a giant. And we’re lucky he’s around.
This small ghostty issue (and some others I can’t recall now) was emblematic of our core disagreement about how we build systems for a broader user base. That’s why I said I get their PoV but disagree with it. I think it would be fair to say using the product reminded me a lot about this particular tension. Reading the GitHub issues even more so. That’s wholly on me.
I am thankful to ghostty for helping me explore many more options. I had been using iterm2 on my laptop and struggling to find something I liked on my Linux workstation. Checking out the new hotness after all the hype still resulted in a net positive.
Nevertheless I am genuinely happy it’s working for you and, again, thanks for your kind and calm response.
Yep - but seeing the thread about it in their github repo was also a turn off. I don’t have to do it with other clients.
I also believe that has to happen on each server - and we’ve got a lot of servers. I’m not particularly keen on needing to change anything to get my terminal emulator to, well, work.
While I get the ghostty team’s PoV - I don’t agree with it.
Ghostty has lots of issues ssh-ing into remote systems that aren’t on the bleeding edge.
I couldn’t get it to work reasonably well enough for me and tried a bunch of others. Currently using Alacritty on both my Linux desktop workstation and Mac Laptop.
I use Zellij anyway and it has all the tab/pane/floating window support I was looking for.
They will never be happy.