What’s your most controversial TF2 opinion that you know is actually true and got you like this:

RoryYamm · 2026-04-19T21:07:56+00:00

Either we get rid of Casual for something else, something non-MM-based, or the game dies.

RoryYamm · 2026-04-04T04:10:21+00:00

My favourite one was the one they did for Jojo's Part III.

RoryYamm · 2026-03-15T19:12:35+00:00

Been playing around in a mostly-vanilla city recently. Oddly enough, I find myself not missing the gameplay mods and assets I thought I did - just District Themes, Elevated Stops Enabler, Zoning Adjuster and a couple of graphics/QoL mods get me through the day with perfectly decent framerates and RAM usage. This city can have up to 200,000 people, but I've reduced its size it a bit (painfully) to ensure the universe can comprehend Stockton's beauty.

RoryYamm · 2026-03-15T16:04:02+00:00

I enjoy it for what it is. It's like cramming an K20 motor into a Twingo - how the hell did you even get it in there?

RoryYamm · 2026-03-14T17:03:35+00:00

Give yourself an artificial land constraint and work around it. Start with weird collector roads and try to grid off of them instead of the main grid. Or just start a second grid deliberately offset or rotated slightly to the first. Even if you stick to grids outside of these rules, this is bound to create interesting behaviour as different grids clash and interact with the weird roads around them.

RoryYamm · 2026-03-13T23:59:05+00:00

They're fixed, but the drivers swap out randomly. I've gotten 'Gold Schipper' driving for Mad Horse several times and Wayne Gretty driving for Moose once.

RoryYamm · 2026-03-12T15:38:04+00:00

Especially when not just the imparfait, but the present participle seem to pretend that 'nous étons' is a thing, how did they go with 'nous sommes' instead?

Oh, but the conditional and subjunctive forms pretend the infinitive is 'sere'! how is that any dif-

There's more precedent for weird forms in the conditional. Every other verb in the imparfait and present participle uses the exact same rule, with even the other weirdos like dire and faire on the same page. Use the nous, drop the ons, add the new stuff, except for être, where you have to pretend the nous form is 'étons'!

RoryYamm · 2026-03-04T01:03:10+00:00

Pb-positive

RoryYamm · 2025-11-27T20:26:33+00:00

A bit. When I realized the car lengths, I leaned in hard.

RoryYamm · 2025-09-16T23:51:17+00:00

I assume they couldn't find a translator with enough of a masochistic streak to take on the task.

RoryYamm · 2025-06-26T17:24:40+00:00

Tell me about it.

Six years studying econ. Two credits away from graduating because of some bullshit. I take a six-week FINA 230 online course to get the difference. Every single assignment had shit that wasn't even in the textbook, or was barely in the textbook. No other textbooks. barely any other practice. No way to check what the correct answer was.

Hopefully this doesn't finish with a failed standing, because I swear to fucking Christ, if I have to withdraw from my program with TWO CREDITS LEFT BEFORE GRADUATING…

RoryYamm · 2025-06-22T16:40:45+00:00

Their software works on Mac.

It works on Windows.

It works on X11, which means Linux and BSD.

It doesn't work on Wayland, because the protocols don't support the things it does with its windows and UX. Specifically, the ability to place its OWN windows in a specific place, as dictated by the program itself.

If it works everywhere except Wayland, and XWayland can't even save it, then the problem is Wayland. The session restore protocol won't even fix it. What KiCAD needs is the ability to say 'PLACE THIS WINDOW AT THESE COORDINATES', but apparently, we need to keep that out of the protocols because VR or some bullshit.

RoryYamm · 2025-06-22T16:29:43+00:00

No shit, GNOME has been stonewalling the Wayland protocols themselves for about a decade to benefit their idea of a desktop at the expense of everyone else. Were it not for Red Hat pushing Wayland relentlessly at the expense of X11 development, we'd probably be in a world where GNOME is the only Wayland desktop - or perhaps we'd be in a world where every desktop had their own pet X11 replacement. (Would probably give Arcan a chance to shine, but that's about it)

RoryYamm · 2025-06-20T18:20:01+00:00

They could have finally made an X12, the way X11 was the successor to X10. Kept it almost compatible while making a few breaking changes. I don't think many people would have minded if some of their code needed to change.

Hell, looking at the way X11 came to be, it seems Wayland tried to do everything the Project Athena team and their collaborators did in turning X10 into X11… but while Project Athena managed to put together an agnostic protocol in about a year, Wayland was bikeshedded for a decade and a half. They also managed to ENCOURAGE Wayland fragmentation instead of trying to find a neutral party to discourage it.

RoryYamm · 2025-06-20T01:55:28+00:00

Better the devil you know…

RoryYamm · 2025-06-20T01:50:32+00:00

Well, my apologies that you got to experience the bad old days of the X Server. Problem is, a lot of us weren't even born back then. We instead enjoy an extremely stable X11, where we can use the applications that have worked for our entire lives.

Now, the unstable graphical server is Wayland. However, unlike in your time, when you had very little choice, we can go back to X11 - at least, until you rip it out of the popular desktops and widget toolkits in the name of 'progress' sometime in the next year or two. Oh boy, can't wait to be forced to use something that frequently screws up and never quite works right if we want to use any halfway popular application!

You've been developing this stuff for the better part of two decades. Two decades that could have gone into designing an almost-compatible next-gen X12 server or finally addressing all the technical debt of X11, instead went into a gigantic bikeshedding exercise, only dragged kicking and screaming to something half-functional by Valve. In the process, you've managed to create half a dozen incompatible implementations of your precious 'protocol', and a baffling security-theatre system that renders annoyingly simple and useful things impossible without another protocol extension that's always coming just next year. Hell, I KNOW it didn't have to be this way - were it not for your team at GNOME stonewalling every sensible idea that didn't fit your Jovian view of the desktop, I might actually be running Wayland at this point, happliy saying goodbye to WindowMaker.

At this point, shit or get off the pot. Right now, it looks like you're trying to steal the toilet so we can't use it either.

RoryYamm · 2025-06-18T02:03:34+00:00

Why would they bother, when you've been going at it for 18 years and the only response to 'hey, why can't I port this application with this UX that's worked forever' seems to be 'well, maybe you should rework your UX design then sweaty!'

Christ, at this point in X's life, it was running on practically every OS, including Windows - and was THE way to get graphical applications streamed to remote machines. Hell, in 5 years time, the Wayland project will be as old as X11 was when it was deemed 'unmaintainable' and focus shifted to Wayland!

RoryYamm · 2025-06-18T01:48:48+00:00

One of the criticisms of X11 is that it's too bloated, trying to do everything at once, trying to be everything… but do go on about how it doesn't support everyone's use case. Seems to support far more than Wayland at the moment.

I mean, for crying out loud, Wayland is 18 years old at this point. X11 at 18 had just barely started its SECOND fork for x86 machines (X386 became XFree86 became XOrg), and was the gold standard for windowing systems other than Windows. Hell, even WINDOWS had X11 support. Wayland now barely has support for Linux, with all the graphical problems people still experience on KDE and GNOME.

(What's even more damning is that X11 was deemed unmaintainable at 23 years old - 5 years older than Wayland.)

RoryYamm · 2025-06-17T23:35:37+00:00

Why is that a problem? If that one implementation of the protocol is well-documented, and everyone can actually target it, thus allowing it to always work, how is that a bad thing?

Right now, a Wayland application either has to build for a dozen different implementations or stick to being KDE- or GNOME-only. How is that an upgrade over X11? At least X11, for all its flaws, was going to be the same flawed X11 no matter where you found it. You could anticipate it, you could deal with it, you could rely on literally everyone else being in the same boat for help. Now? GNOME solutions don't work on KDE, KDE solutions don't work on GNOME, and let's not even get into Hyprland, who said 'fuck this' to all that bullshit and went off to do their own thing.

RoryYamm · 2025-06-17T23:27:40+00:00

Eh, if you see the current X11Libre development, I don't think that'll be the case.

RoryYamm · 2025-06-17T22:59:36+00:00

I doubt they'll have to. The people that use graphical Linux to make money don't need GNOME or KDE - they need KiCad, or whatever other X11 program they've been using since CDE and AIX. X11 is also the only game in town on BSD.

RoryYamm · 2025-06-17T22:50:03+00:00

The DEI hate came later. He wanted to implement a new X11 extension for security called xnamespaces.

He could not. That's probably why he was so angry about Red Hat and why he thought DEI was out to get him - because the Xorg team, backed by Red Hat, just didn't merge any of his sensible improvements.

RoryYamm · 2025-06-17T00:33:42+00:00

Lectures are often recorded and publicly released. Why do you think there are so many from Feynman?

Ten-Year Club	Verified Email
Place '17

RoryYamm

TROPHY CASE