Tell me your company leadership has ADHD without saying it.

Have they actually worked with Valve before? How could they be dumb enough to not reach out first?

Or was this maybe an attempt to strong-arm Valve into granting them a license? Like, did they expect them to go, “well shit, you’ve got so many preorders now I guess we’ll have to sign off on it”?

Or did they simply expect Valve not to care?

These might be sold separately but don’t cheap out, if you want them to wear evenly then replace both at the same time.

But base wage for those positions is also significantly lower than minimum wage because the tips are expected to compensate for it, so the ceiling is higher but the floor is also lower. So refusing to tip at all does kind of make you out to be the asshole.

Unfortunately most people are just trying to survive and don’t really have the time or the energy to worry about the bigger picture.

Personally, I just split the difference and refuse to tip anywhere it’s not already factored into the wage structure. It’s not gonna change the situation but at least it helps hold the line.

The problem is the workers who get tips generally like it because they can potentially make a lot more than a comparable fixed wage. On a good night you can make several times over the base wage, and under-report cash tips on your taxes (or omit them entirely, but the IRS might catch that).

So a lot of workers don’t want tipping to go away any more than the restaurant owners do.

I’ve been saying this for a while: without opining whether or not machine learning models are even capable of consciousness, there’s no way in hell LLMs are.

These are once-through, completely immutable models. Any activity that could be remotely construed as “thought” evaporates the instant it outputs a token, and then it starts over from scratch.

Good fucking luck being conscious when your consciousness only exists for a fraction of a fraction of a second at a time.

Ah right, so that would be a 3D array.

• T* is a single row of T
• T** is a list of rows
• T*** is a list of “layers” in the third dimension

This would be incredibly hazardous to pass around as a bare pointer with no context, though. I’d expect to see this in a struct that, at minimum, also includes fields for the size of each dimension.

Real talk: is there any practical use-case for T*** of any pointee type?

And people who have a particular interest in that culture would be termed… Saxophiles.

The Internet has ruined me because I can’t read the word “watersports” without thinking of the fetish anymore.

Makes sense, it’s a lose-lose. No matter which way you go with the story (or the gameplay, for that matter), it’s gonna piss a lot of people off because it doesn’t meet their ridiculous expectations.

Some sequels just aren’t meant to be. Better off remaining vaporware than ending up some disappointing, soulless cash grab.

A little flag pops out that says “bang!”

When you cargo install a binary, it ignores lockfiles. If you clone a project and build it, it respects the Cargo.lock that was checked in.

It’s not enforced though, and there’s no way as a consumer to see how a crate was published.

To be extremely fair, crates.io has a huge maintenance bottleneck because AFAIK it doesn’t even have a single dedicated developer. But that’s definitely a big part of the problem.

The Rust Foundation is really just not pulling in enough revenue to support the project properly. They really ought to figure out more revenue streams than just sponsorships and donations.

You can’t overwrite previously published versions.

Application projects are recommended to check-in the Cargo.lock which pins dependency versions but you can always just run cargo update at any time which automatically upgrades all dependencies to the newest version allowed by the Cargo.toml.

Some projects get around this by pinning the dependency in the Cargo.toml (using =) or by vendoring all their dependencies, which is a huge pain in the ass.

Interestingly, developers in ecosystems like Go, Rust, and those utilizing native Web APIs—where robust standard libraries drastically reduce reliance on third-party code and strict cryptographic verification is built into the core toolchain—reported zero instances of a college dropout’s weekend project wiping out global logistics infrastructure today.

As someone who’s built a career in Rust, it is 100% susceptible to an attack like this. The community is just generally paranoid enough to avoid depending on super niche packages.

Even so, Cargo still doesn’t have code signing and crates.io doesn’t have 2FA. They just barely rolled out email alerts for new crates being published with your API key.

And there’s dozens of single-author crates that are depended upon by millions of lines of code, any one of which could easily be a vector in a supply chain attack. In fact there have been attempted supply chain attacks against crates.io, but to my knowledge they’ve all relied on typo-squatting.

We’re definitely overdue for a major attack.

“Why don’t we just skip the middleman and I fuck you instead?”

What happens when the baby turns to red mist? Is that just “part of God’s plan”?

This is something we lost when game developers stopped publishing free demos. I cannot imagine how “just buy it and refund it if you don’t like it” is somehow better for the industry.

Freddie had power bottom energy tho

That song was actually written by guitarist Brian May.

So this dude:

Is the real ass-man of Queen.