I just put this into YouTube search and got results that contraindicate your claim¹:

> "sanic" the hedgehog

The quotes seem to shut down autocorrect

1: there's nothing that I see about the T-shirt, but the first result is titled "Sanic DA hedgeh0g". I will not be looking at what this video is. Several other results also include the word "sanic" in relation to the hedgehog.

Did you mean to respond to one of the sibling comments that are talking about autocorrect? I don’t understand what would be contradictory between what I said and what you said.

Just stick XFCE on a modern minimal-ish (meaning not Ubuntu, mainly) distribution and you'll have this with modern compatibility. Debian and Fedora are both good options. If you want something more minimal as your XFCE basd, there are other options too.

XFCE is saddled with its GTK requirement, and GTK gets worse with every version. Even though XFCE is still on GTK3, that's a big downgrade from GTK2 because it forces you to run Wayland if you don't want your GUI frame rate arbitrary capped at 60 fps.

For people wanting the old-fashioned fast and simple GUI experience, I recommend LXQt.

It makes it easier to treat the computer as part of your own body, allowing operation without conscious thought, as you would a pencil or similar hand tool.

> What use is there in display frame rates above 60 fps?

On a CRT monitor the difference between running at 60 Hz and even a just slightly better 72 Hz was night and day. Unbearable flickening vs a much better experience. I remember having some little utility for Windows that'd allow the display rate to be 75 (not 72 but 75). Under Linux I was writing modelines myself (these were the days!) to have the refresh rate and screen size (in pixels) I liked: I was running "weird" resolutions like 832x604 @ 75 Hz instead of 800x600 @ 60 Hz, just to gain a little bit more screen real estate and better refresh rate.

Now since monitors started using flat panels: I sure as heck have no idea if 60 fps vs 120 fps or whatever change anything for a "desktop" usage. I don't think the problem of the image fading too quickly at 60 Hz that CRT had is still present. But I'm not sure about it.

120 FPS vs 60 FPS is definitely noticeable for desktop use. Scrolling and dragging are night and day, but even simple mouse cursor movement is noticeably smoother.

Outside of gaming, not much. However, now that I'm used to a 144Hz main monitor, there is no world where I would get back. You just feel the difference.

So basically, no use when you've not tasted 120+Hz displays. And don't because once you do, you won't go back.

Mine supports variable refresh rate, which means for most desktops tasks (I.e when nothing is moving), it runs at 48Hz.

Incredibly, Linux has better support than windows for it on the desktop: DWM runs full blast, while sway supports VRR on the desktop. Windows will only enable it for games (and games that support it). Disclaimer: Wayland compositor required.

It’s not enabled by default on e.g. sway because on some GPU and monitor combos, it can make the display flicker. But if you can, give it a try!

Windows 11 idles at around 60 Hz in 120 Hz modes on my VRR ("G-SYNC Compatible") display when the "Dynamic refresh rate" option is enabled, and supports VRR for applications other than games (e.g., fullscreen 24 FPS video playback runs at 48 Hz* via VRR rather than mode switching, even with "Dynamic refresh rate" disabled).

* The minimum variable refresh rate my display (LG C4) supports is 40 Hz.

Ah, then Windows 11 has at least one improvement compared to Windows 10 as far as user experience goes. Good to know, as I never made the jump

I use KDE + Nvidia, and last I looked into it, it only worked if you had one monitor enabled. That's fine for gaming, not for working.

But it has been a while since I've tried it, maybe I should look into it again

AFAIK it’s very compositor-dependent. Works fine with disparate monitors on Sway + NVIDIA (1x144 VRR, 2x60 no VRR + 1x120 VRR when the TV is on).

The state of Wayland compositors move fast, so support may be here. Last thing I’m waiting for is sway 1.12 that will bring HDR.

I, for one, lose track of the mouse way less often at 165Hz.

I lose track of the mouse less often at 1024x768!

You need a bigger cursor.

MXLinux is really great for something like xfce and I really loved the snapshotting feature of it too. Highly recommended.

I have seen things approved by those sort of organizations that were extremely dangerous, such as a listed fire alarm that when installed has a significant chance of becoming silently deactivated.

With that said, it can be even worse when it isn't listed.

The newer Android version could simply give empty data (for example, location is 0,0 latitude longitude, there are no visible WiFi networks), when the permission is missing and an app on the old SDK version requests it.

Of course, they don't like this because then apps can't easily refuse to work if not allowed to spy.

That can have some very extreme legal ramifications.

Consider - it's a voip dialing client which has a requirement to provide location for E911 support.

If the OS vendor starts providing invalid data, it's the OS vendor which ends up being liable for the person's death.

e.g. https://www.cnet.com/home/internet/texas-sues-vonage-over-91...

which is from 2005, but gives you an idea of the liability involved.

Phone companies are required to make sure 911 works on their phones. Random people on the internet aren't required to make sure 911 works on random apps, even if they look like phones.

The comment you're replying to literally has an example of an internet calling service being fined $20,000 for not properly directing 911 calls.

I guess Vonage should try to appeal the case and say pocksuppet said they're not required to do that.

Vonage sells phone services that happen to use the internet. This is not the same as being WhatsApp.

It can't have "extreme ramifications", Google's own phone couldn't call 911 for a while.

And you can manually force only the voip dialing apps instead of everyone

> I can make it do basically anything I want

X11 can't do high refresh rates every time that I've tried to do so.

It runs just fine at 165 hz for me. Given that xrandr and CRTs have been around for a while, and both have supported high refresh rates for a long while, something seems fishy here. Something is probably at fault, but it's not X11.

X11 can't do different hz on different screens. If you have a dual screen setup where one screen is 165 hz and the other is 60 you're SOL.

Works fine for me with 144/120 with the second as 60.

What's happening is you are running both screens at 144/120 and your 60 is gonna have vsync and screen tearing issues.

What vsync issues?

Couldn't you stop tearing with a couple lines of code? Don't swap out buffers mid-frame, very simple.

The simple solution doesn't make 144+60 look super smooth, but 120+60 should be almost perfect.

How does wayland handle the hypothetical problem of playing a 24 fps movie split across a 48hz and 60hz display?

(Hint: It’s not possible to solve correctly.)

You joke, but the wayland protocol leaves this up to the compositor. Nothing in the protocol prevents your desktop environment from doing this.

I heard the desktop environmentalists are working on such a project.

It is able to output the high Hz to the display, but the desktop (like window decorations and window dragging) remains at 60 Hz, it looks like. Individual windows can still successfully render at high Hz. Contrast this with Wayland where I've always seen everything go at the high speed, even if I'm using the same DE in both (like Gnome Wayland and Gnome Xorg on the same hardware).

Huh ? It did in 2000.

> Why would a player knowingly choose to play on matchmaking that is advertising no anti-cheat?

My understanding of the proposal is that it advertises no invasive anticheat (meaning mostly rootkit/kernel anticheat). So, the value proposition is anyone who doesn't want a rootkit on their computer. This could be due to anything from security concerns to desiring (more) meaningful ownership of one's devices.

There is a lot of merit to this view, but there is also a major problem: rules like this make it substantially harder to start a new business due to increasing overhead and complexity, which is bad for everyone long term. Such comparatively more complex and burdensome regulation is why so many (but not all) startups go to America or Israel instead of Europe.

To address this I prefer ultra low friction and ultra low cost regulations over complex and performative schemes. For example, GDPR requires the appointment of a "data protection officer" in some cases, which is mostly just an extra fee for small companies. Instead, it should only regulate the rights (such as to be forgotton, etc.). Appointing such an officer is mostly performative.

The most important thing in my view is that both parties are aware of their rights and responsibilities. If the plain text of the warranty agreement specifies replacement, replacement should be required. If the business doesn't want to assume the risk, that's fine, but the warranty should then clearly and explicitly stipulate replacement or refund at the retailer's discretion, in such a way that an average consumer would be expected to see and understand this (i.e., no "replacement" in large, friendly letters and "or refund" buried in fine print or legalese, or leaving out specific details to be filled in by default provisions when such provisions favor the retailer).

I'll take fewer startups if the tradeoff is actual consumer and human rights. I don't even think it's a morally debatable tradeoff.

I don't think that it's that simple. I'm advocating for regulations to consider the burden on small businesses and aggressively minimize it.

Another example than the GDPR example that I previously gave is beneficial owner registration. The US government tried to pass a law requiring every corporate entity to state who the beneficial owners are, to reduce tax evasion. In principle, this sounds great, but the vast majority of corporate entities are small businesses with natural persons owners, so that beneficial owner is already obvious. So, they should have added such an exception to filing requirements. Even better would be to just work with states to put beneficial owner fields on the existing state incorporation forms, instead of creating a new form, that are optional to fill in when the owner is a natural person. That way, we reduce tax evasion with the better data, but we aren't relying on a random electrician in Ohio or a tech nerd startup founder in California to be aware of these requirements. While one form isn't a big deal on its own, the whole system is like this, and it adds up.

Such miscommunication (varying levels of taking it literally) is also common with autistic and allistic people speaking with each other

This matters when you're hiding from the website. It doesn't matter if you're just trying to hide such things from the public.

It also matters if you're trying to hide from subpoenas to the website.

> even a really cool library that makes Rust do this.

The first library that comes to mind when I think of this is `serde` with `#[derive(Serialize, Deserialize)]`, but that gives persistence-format output as you describe is preferable to the former case. I usually use it with JSON.

So, this seems like it may be a false dichotomy.

Maybe a little bit. But serde works with JSON (among other formats), and you can use it to read and write JSON that interoperates with other libraries and languages just fine. Kind of like how SQLAlchemy looks kind of like you’re writing normal Python code, but it interoperates with SQL.

rkyv is not like this.