The Wayland spec doesn’t allow for clients to arbitrarily get clipboard data under typical conditions. Since most applications these days are running under Wayland, it should be that copying to the clipboard isn’t exposed to X11 clients most of the time (only when copying from or pasting into XWayland).

You can somewhat mitigate that with different sorting options, but afaik there is no option at all to hide games unavailable or unowned on the current account.

Does “ready to play” filter those out?

The topic of the talk was how Rust eliminates classes of errors (and security issues) that are being very frequently found and reported. An example given: you can’t forget to lock/unlock when using the locking types in Rust.

That Rust can be (and has been) used in AI and crypto projects isn’t relevant to this argument.

I’m not sure if you are aware, but “12+20,” “color picker red,” and “what is -40 degrees c in f” already give you the answers you want in DuckDuckGo without needing to click on a search result.

It isn’t super smooth to configure yet, but it should be possible to use HDR. Have you tried that?

If you do decide to get the Steam Machine, you can stream from there to get a lot more out of the Steam Frame than what it can do standalone.

Considering Beat Saber already works on Linux just fine, and it isn’t particularly demanding/runs fine on less powerful standalone headsets, I imagine it’ll work.

This is one of the changes I’m most frustrated with, and one I didn’t expect. Maybe it feels worse for me because I didn’t expect it, unlike some of the other compromises.

I’ll still buy one, but I don’t like this change.

EDIT: The other big disappointment that I knew was possible but didn’t expect was the loss of Lighthouse tracking.

Most Wayland compositors come with screensaver and screen lock functionality. Some have an API for custom screensavers.

I have a couple Dell laptops (from my work) with firmware in LVFS, and it is so nice how easy it is to use. I hope that this change encourages the biggest vendors to give some money to help keep it going.

It is fair to have a preference for exceptions. It sounds like there may be a misunderstanding on how Option works.

Have you used languages that didn’t have null and had Option instead? If we look at Rust, you can’t forget not to check it: it is impossible to get the Some of an Option without dealing with the None. You can’t forget this. You can mess up in a lot of other ways, but you explicitly have to decide how to handle that potential None case.

If you want it to fail fast and obvious, there are ways to do this. For example you, you can use the unwrap() method to get the contained Some value or panic if it is None, expect() to do the same but with a custom panic message, the ? operator to get the contained Some value or return the function with None, etc. Tangentially, these also work for Result, which can be Ok or Err.

It is pretty common to use these methods in places where you always want to fail somewhere that you don’t expect should have a None or where you don’t want your code to deal with the consequences of something unexpected. You have decided this and live with the consequences, instead of it implicitly happening/you forgetting to deal with it.

For this example, I feel that it is actually fairly ergonomic in languages that have an Option type (like Rust), which can either be Some value or no value (None), and don’t normally have null as a concept. It normalizes explicitly dealing with the None instead of having null or hidden empty strings and such.