You could use Mos, which also has the advantage that smooth scrolling works the same in every app (speed, acceleration etc)

https://mos.caldis.me/

It is mentioned

Ah yeah, you are right. It was easy to miss, as it was ~30 words in a massive article.

What artificial sweetener is in regular Coke?

Apart from just running Linux apps, you can use this to run graphical applications remotely on a Linux server, like X11 forwarding.

I thought Wayland was different from X11, and didn't allow this. But I'm far from an expert on this topic so I'd like to learn more.

https://github.com/neonkore/waypipe proxies Wayland over a network. It’s straightforward enough in theory: Wayland core is just a communications protocol plus shared memory; so you just need to forward the messages, and detect and send changes in the shared memory. Not the cheapest thing, but perfectly tractable. Of course, there are also more difficult extensions, like GPU integration, but that sort of thing was a problem for X as well.

This is how modern x11 worked too since nobody uses software rendering with x primitives anyway.

Wayland natively isn’t built for forwarding the way X11 is. Waypipe fixes this, providing an X11 protocol equivalent for Wayland. This project is a waypipe client for macOS.

here is Wayland vs X11 visualised.. it might help - https://vectree.io/c/compositing-window-management-architect...

According to that page Wayland's architecture is simpler than X11.

If you put everything into a monolith, it looks simpler than if you have components that have to speak protocols to each other.

Rio and its predecesor in Unix v8/v10 did it better than X. In some cases we got the worst:

- POSIX bloat vs Plan9's simple C and even simpler API

- ioctl's vs everything it's a file

- Complex socket spawning vs open() and dial() under Plan9/Go

- ALSA vs tuned up OSSv4, or plaing audio/mixerfs under 9front

- find -which syntax is huge- vs walk -f (or -d for dirs) | grep

- RDP/VNC/SSH/NFS/SMB vs just rcpu+auth (9p) and run rio(4) and for files... 9fs which does a simple bind()

- Symlinks and hard links vs bind and namespaces.

- GDB and SSH vs importing a remote /proc in a rio window and remote-debugging your damn remote machine as if it were your own. How cool is that? Ditto with devices. Import sound cards, network cards with the whole IP stack. NAT you say? No more.

- FFSv2 (hello OpenBSD) vs current GeFS under 9front which is like a miracle over what OBSD it's trying, the bad ZFS license or BTRFS not being ready on GNU yet. Probably the Hurd people will port GeFS to Hurd/Mach first, before BTRFS gets even ready...

- Dynamic vs static linking. 9front, a suite of multiarch compilers. Set $objtype, compile, link, deploy a standalone binary. Ready, as if it were a Go binary under Unix, but without glibc oddities. ARM binaries from 386? Done. You need a crazy long i686-gnu-foo-bar and the rest of crazyness? Not anymore. These come in src form, compile and install them, no internet required. Literal two damn commands to do so, from any to any arch.

- SH/KSH/Bash. Complexity ridden shells. Here's rc. No aliases there, just functions. No complex escaping, just () for strings, ^ to concat, ' ' for quoting. Problem solved. Even the conditonal words' syntax it's like throwing down all the complexity giving you a weirdly simple shell.

- PCRE and ex commands under vi/nvi/vim (bloat) vs Sam and structural regexes. Sam it's like a graphical vi, period, there's nothing alien of it. Imagine a modeless vi with a small frame to input commands with an easier syntax:

     x/lookup/c/replace 

These can be chained with ease.

Maybe try this: https://ke-complex-modifications.pqrs.org/#pc_shortcuts

Yeah I've used Karabiner to get windows-style shortcuts (home/end, etc.) and it works very well.

See also https://github.com/Sportinger/MasterSelects

The "Email Image..." one is infuriating. Who right clicks an image to email it to someone in 2026? And if it's you, could you help me understand why??

Every random app now-a-days has share buttons. Why shouldn't the browser have on, when it is inherently about browsing a network resource?

It's still more useful than the "Set as desktop background" entry.

Or the manual, which describes the features for automatically handling it.

If I install a terminal and SSH doesn't work from it out of the box, I would describe that as a bug and wonder if I need to read the full manual to not fall foul of other gotchas

It is a bug.. But not with Ghostty...

What do you think the bug is, exactly?

Servers throwing "missing or unsuitable terminal" even when the connecting terminal is available and very suitable. And this is just because they hardcode xterm as the "standard".

>Sure, if you think calculators or bicycles are "superhuman technology".

Uh, yes they are? That's why they were revolutionary technologies!

It's hard to see why a bike that isn't superhuman would even make sense? Being superhuman in at least some aspect really seems like the bare minimum for a technology to be worth adopting.

By "superhuman" the LLM cultists mean "the singularity", "brain in a chip", "eternal life via digitization" and the rest of the claptrap.

Don't let them off the hook.

Those icons were incredibly visually distinct, despite being meaningless. I still know exactly what they are for instantly, in my peripheral vision, years after using many of them.

Modern icons are not only not comprehensible but not visually distinct (Tahoe making everything the same shape, many apps removing all colour from toolbar icons, various distinct if anachronistic symbolic icons like Save being replaced with slighly different orientations and arrangements of arrows and rounded rectangles...).

This severely impacts the efficiency of user interaction, especially after the first time you use something, at least for me. It's not a knee jerk reaction, it's a reaction to actually feeling it becoming harder to use my computer.