I’ve never seen a repo so reticent to tell you what it is.
My guess is it’s the journal software running the .org but everything also seems to be down half the time.
I’ve never seen a repo so reticent to tell you what it is.
My guess is it’s the journal software running the .org but everything also seems to be down half the time.


Complete non-story. The Deck has been out for years for this verification to mature and it’s usually less about specs (in the age of FSR/DLSS etc.) and more about “can this game be played with this control scheme comfortably” which is not an issue for the Steam Machine since it’s just a PC.
This is definitely about the D language, I just haven’t heard anything about in a long time (since Rust ate its lunch) and nothing about it using AI or long time devs leaving.
Was there drama with D? I’m out of the loop…


Do you think benchmark results like these are meaningful when comparing Linux distributions?
Almost never. Bumping the minimum architecture version and optimization levels is all well and good, but unless you’re doing tons of vector oriented workloads it’s not going to qualitatively make a difference.


I’m a couple years younger than you, but a lot of this resonated for me. Custom installers were some of my early inspirations for making apps that didn’t have the traditional gray box aesthetic.
However, I will say that Kenshin was a thing in the US. Samurai X was only the name of the OG movies where he was still lethal AFAIK.


Yeah, couldn’t care less if Chrome is faster when it is controlled by Google and actively working against extensions.
Not to mention we crossed a performance line maybe 10 years ago where browser engines on modern processors are basically trivial. Once we started having 8+ threads and the browsers got smart enough to leverage them, I’d bet bandwidth (or memory if you have many tabs), is a way more typical bottleneck.


Oh, that makes more sense, but then “unsigned” void?


Okay, U8, sure, but a boolean is U0? Surely U1 if you absolutely must…
Agreed. I was an early Wayland convert because once upon a time I started writing a WM and taking an interest in X internals… And then my face melted off like I’d opened the Ark of the Covenant.
Things are so much simpler now.
Wayland is a sports car - modern, tailor made for performance. X is like a '99 Civic that’s had the seatbelts stripped out and the airbags replaced with cameras that let all the other cars on the road see you naked.
It’s fine to prefer X, but the older it gets the more people are going to roll their eyes at you. XWayland is fine for random old stuff, but there is zero reason X should be running your whole display these days.
Inb4 someone mentions network transparency that gimps the rest of the system or some 5000 year old app that needs to sniff events sent to every other program.


I have this setup with Plasma, and it is probably easier to do this at the Linux level. I added this to my kernel command line: drm.edid_firmware=DP-1:edid/lg-ultra.bin video=DP-1:3840x2160@60e
Where that EDID file I dumped from a spare monitor using a method I got here.
Anyway, it can be tricky to pick the right device, but I can confirm Sunshine sees it and works properly, and it can be managed like a normal monitor.
Look on my works Sim Mayor and

This better not awaken anything in me…
It’s basically the best virtualization platform. It can do full system emulation across a number of platforms, or hardware assisted virtualization (using KVM). It’s incredibly useful for debug as well as doing real work.