I've been pretty happy with Wayland for the past ~2 years of using it.
- No annoying "X11 stutter"
- FreeSync works reliably; no more fucking around with different compositors.
- applications aren't allowed permanently alter the display settings. That was particularly problematic with older Windows games and wine. Depending on the game, exiting a game could leave the display server in a very low resolution on exit. Even worse, a few games would result in the X11 gamma settings being altered outside of the game (Deus Ex was one, but there were a few others).
- display-specific scaling factors
- I could use Waydroid on my 2-in-1 finally.
- HDR support. As an added bonus beyond HDR content, SDR content looks better on my PG42UQ monitor due to the monitor suffering from severe black crush in SDR mode.
- Running CEF (Chromium) in Wayland mode does NOT respect the system scale factor. The workaround is to run it X11 mode. Not too big of a deal since I'm using CEF in offscreen-rendering mode with a Wayland SDL surface, but annoying.
- Picture-in-Picture isn't widely supported yet. It is one of those things that Wayland is building _towards_ rather than X11 just working.
- Minor, but not being able to position the window centered on startup is kinda annoying.
So yeah - tradeoffs, but currently good enough for me and it continues to get better. I'm optimistic.
I've been running Claude Code in a Docker compose environment with two containers - one without Claude that has all the credentials setup and a Claude container which transparently executes commands via ssh. The auth container then has wrappers which explicitly allow certain subcommands (eg. `gh api` isn't allowed). The `gh` command in the Claude container is just a wrapper script which bassically `ssh auth-container gh-wrapper`.
Lots of manual, opinionated stuff in here, but it prevents Claude from even accessing the credentials and limits what it can do with them.
Yeah - that part is disappointing as well. I'd be glad if it included Wayland support, native touch input, full OpenGL and Vulkan support - but I'm not counting on it.
Not out of the box, though. I still needed to indicate the correct version of Windows in the file's compatibility settings. Windows XP SP3 worked like a charm.
An Apple Watch with a cellular connection, paired with Airpods, fulfills some of the role of a small iPhone - you can make calls, listen to music, and even do some light texting if Siri likes your accent.
I love my apple watch but I can safely say i've never done any of the above with it. It's too much of a pain to switch the bluetooth headphones to it and the screen is too small to do much actual computing with it. The fitness aspects are totally worth the money, though.
In my experience copying from some programs preserves long lines. Copying from other programs breaks them at the wrap point. Once the text is cut into lines, pasting can't fix it. I'm not at my computer now so I can't give factual examples. I guess that copying from the output of cat file on a terminal is one of those unfortunate cases.
> I guess that copying from the output of cat file on a terminal is one of those unfortunate cases.
It depends on the terminal. Some will actually preserve the line breaks vs soft wraps. Those terminals will reflow the text when you resize the window.
But if you already have the file you might as well run something like `xclip <file` to copy its contents directly to the clipboard.
> In the professional world, I see software developers blindly copying and pasting code suggestions from LLM providers without testing it, or understanding it.
When you see that, call them out on it. Not understanding copy+pasted code is one thing, but not testing it is a whole other level of garbage.
- No annoying "X11 stutter"
- FreeSync works reliably; no more fucking around with different compositors.
- applications aren't allowed permanently alter the display settings. That was particularly problematic with older Windows games and wine. Depending on the game, exiting a game could leave the display server in a very low resolution on exit. Even worse, a few games would result in the X11 gamma settings being altered outside of the game (Deus Ex was one, but there were a few others).
- display-specific scaling factors
- I could use Waydroid on my 2-in-1 finally.
- HDR support. As an added bonus beyond HDR content, SDR content looks better on my PG42UQ monitor due to the monitor suffering from severe black crush in SDR mode.
That said, there are annoyances. I recently started work on a rewrite of the Jellyfin Desktop client (https://github.com/jellyfin-labs/jellyfin-desktop-cef) and of course targeted Wayland first:
Pros:
- HDR via an Wayland subsurface works great!
Cons:
- Running CEF (Chromium) in Wayland mode does NOT respect the system scale factor. The workaround is to run it X11 mode. Not too big of a deal since I'm using CEF in offscreen-rendering mode with a Wayland SDL surface, but annoying.
- Picture-in-Picture isn't widely supported yet. It is one of those things that Wayland is building _towards_ rather than X11 just working.
- Minor, but not being able to position the window centered on startup is kinda annoying.
So yeah - tradeoffs, but currently good enough for me and it continues to get better. I'm optimistic.