I agree that going for wages in the traditional sense doesn’t catch many of the most relevant income streams. However, I think that a “maximum wage” makes sense as a theoretical construct used to create a sensible income tax scheme.

Essentially, tax brackets and rates could be defined in relation to the median income. Go too far above that (hitting the “maximum wage”) and your tax rate rapidly increases, maybe even going as high as 90%. Of course this would have to cover all sorts of income, not just plain money.

This scheme would effectively box people into a certain band of acceptable wealth and would create an incentive to raise wages – after all, if the average worker makes more, so can the most wealthy.

(Also, full agreement on needing to talk about better labor protections. American labor law is really lax.)

Mind you, people probably don’t think of your standard high earner they they think of an income cap. They think of people who make four (or even five) digits an hour, a rate that maybe high end lawyers can match. Maybe.

CEOs of large companies can easily make that much, often not even tied to performance but contractually guaranteed. The super-rich make that much simply by existing.

Basically, if your labor (or mere existence) isn’t even worth 1000 bucks an hour to your clients you’re a peasant like the rest of us and an income cap is probably never going to be relevant to you.

Especially if you didn’t have a lot of spare time. With an active community you can just dip into discussions when you have the time. With a community you’re trying to establish yourself you absolutely have to provide a steady stream of content until it (hopefully) takes off.

The software development industry version of this is “we really need to fix that soon but it’s beyond the scope of this PBI”.

“Soon” is a shorthand for “we’ll put this on the backlog and never pull it into a sprint until it blows up in our faces, at which time we will gripe about how nobody bothered to fix it earlier”.

But you can tune the specifications of the yarn to theoretically make the socks up to 2% more comfy. In practice your tuning efforts will make the socks less comfortable and tear more easily.

Exactly. If this was “Marathon: Return to Deimos” or “Marathon: Battleroid Arena” or even “Marathon Infinity Plus One” I wouldn’t complain. Much.

But just taking the name (and logo) of the original one? The game that started Bungie’s path towards being one of the big names of the FPS genre? That’s like saying they went straight from Pathways Into Darkness to Halo. That’s not honoring Marathon, it’s a soulless recycling of an old IP.

My vent cores feel distinctly unblasted.

We know that people have different chronotypes. We even know that most people of working age aren’t really morning people. Unfortunately, our business world assumes a standard circadian rhythm and is structured around getting up early because people needed to use every bit of daylight way back when. So that sucks, especially if you’re an evening or even night person.

Man, I hate it when they make new games that have exactly the same name as an older game by the same company. And this one’s not even a remake. I have no idea if Marathon (1994) and Marathon (upcoming) even play in the same universe but they don’t seem to have much in common gameplay-wise. Ugh.

Makes me wanna install M1A1 Aleph One (didn’t know it does M1 directly these days) and shoot some Pfhor, though.

“You finished a computer game, Atticus.”

The truth was a burning green crack through my brain.

Credits scrolling by, a reminder of the talent behind a just-finished journey. The feeling of triumph, slowly replaced by the creeping grayness of ordinary life.

I had finished a computer game. Funny as hell, it was the most horrible thing I could think of.

There are many OS-related diseases. Many Linux users are affected by or at least know someone who suffers from the compulsive need to mention that they’re using Arch. Then there’s compiler flag addiction, which can develop in Gentoo users. iDependency, the pathological need to purchase any product Apple releases, has financially ruined many macOS users. Windows users’ feelings towards Windows Update and the associated increase in heart rate are known to substantially increase the risk of a fatal heart attack.

Knowing how to operate TempleOS is considered a mental disorder under the DSM-5.

I’d argue that unfun design elements can be useful in games if used with care and purpose. For instance, “suddenly all of the characters you’re attached to are dead” is not exactly fun but one of the Fire Emblem games used it to great dramatic effect at the midway point.

Of course the line between an event or mechanic that players love to hate and one they just hate is thin.

Hoo boy, you weren’t kidding. I find it amazing how quickly this went from “the kernel team is enforcing sanctions” to an an unfriendly abstract debate about the definition of liberalism. I shouldn’t, really, but I still am.

Aw, c’mon! Who doesn’t enjoy piping ten megabytes of JavaScript through Webpack to achieve those crucial on-scroll effects on an otherwise static page?

Oh yeah, the equation completely changes for the cloud. I’m only familiar with local usage where you can’t easily scale out of your resource constraints (and into budgetary ones). It’s certainly easier to pivot to a different vendor/ecosystem locally.

By the way, AMD does have one additional edge locally: They tend to put more RAM into consumer GPUs at a comparable price point – for example, the 7900 XTX competes with the 4080 on price but has as much memory as a 4090. In systems with one or few GPUs (like a hobbyist mixed-use machine) those few extra gigabytes can make a real difference. Of course this leads to a trade-off between Nvidia’s superior speed and AMD’s superior capacity.

These days ROCm support is more common than a few years ago so you’re no longer entirely dependent on CUDA for machine learning. (Although I wish fewer tools required non-CUDA users to manually install Torch in their venv because the auto-installer assumes CUDA. At least take a parameter or something if you don’t want to implement autodetection.)

Nvidia’s Linux drivers generally are a bit behind AMD’s; e.g. driver versions before 555 tended not to play well with Wayland.

Also, Nvidia’s drivers tend not to give any meaningful information in case of a problem. There’s typically just an error code for “the driver has crashed”, no matter what reason it crashed for.

Personal anecdote for the last one: I had a wonky 4080 and tracing the problem to the card took months because the log (both on Linux and Windows) didn’t contain error information beyond “something bad happened” and the behavior had dozens of possible causes, ranging from “the 4080 is unstable if you use XMP on some mainboards” over “some BIOS setting might need to be changed” and “sometimes the card doesn’t like a specific CPU/PSU/RAM/mainboard” to “it’s a manufacturing defect”.

Sure, manufacturing defects can happen to anyone; I can’t fault Nvidia for that. But the combination of useless logs and 4000-series cards having so many things they can possibly (but rarely) get hung up on made error diagnosis incredibly painful. I finally just bought a 7900 XTX instead. It’s slower but I like the driver better.

Speak for yourself. I’m going to migrate all of my 22-bit RSA keys to a longer key length. And not 24 bits, either, given that they’re probably working on a bigger quantum computer already. I gotta go so long that no computer can ever crack it.

64-bit RSA will surely be secure for the foreseeable future, cost be damned.

I also only used v2 but it’s the extra stuff in it that slightly annoys me. Like how turbo mode (brighter than the usual maximum but usually time-limited to avoid overheating) is only available when the full UI is unlocked. Or how there’s a stepped ramp mode that I have to remember to disable whenever I swap out the battery. Or how I can accidentally enter one of the more exotic modes of for some reason I press the button too often.

Anduril is way overengineered. I like this UI that some of my lights have:

While off:

• One push: Turn on at the last used brightness.
• Two pushes: Turn on at maximum brightness.
• Three pushes: That strobe mode that you don’t need but seems to be obligatory.
• Hold: Turn on at the lowest brightness (or moonlight mode if the light has one).

While on:

• One push to turn off.
• Two pushes to toggle between maximum brightness and the last used “regular” brightness.
• Three: That strobe mode that someone has to have some use for.
• Hold: Alternately increase or decrease the brightness.

That’s pretty easy to learn and gives you all the functions you’d reasonably need (plus that strobe) without a lot of clutter.

We used to have one: “Solang das deutsche Reich besteht wird jede Schraube rechts gedreht.” (“As long as the German Empire persists every screw is turned right.”)

Given that the German Empire failed spectacularly, this sentence isn’t very popular anymore.