yeah, I helped raise hw requirements for two servers recently, an alternative to nvidia wasn’t even on the table

we’re talking GPUs, idk why you’re bringing FPGA and CPUs in the mix

That sounds like a coin flip, but 50% reliability can be really useful.

If a model has 50% chance of completing a task that would cost me an hour - and I can easily check it was completed correctly - on average, I’m saving half of the time it would take to complete this.

That said, exponentials don’t exist in the real world, we’re just seeing the middle of a sigmoid curve, which will soon yield diminishing returns.

this openai partnership really stands out, because the server world is dominated by nvidia, even more than in consumer cards.

they pay because AMD (or any other for that matter) has no product to compete with a 5080 or 5090

probably the owner of the pictured sword phone

mike tyson is two pigeons

You’re not a developer.

shit, don’t tell my employer

personally, I’ve heard a lot more “bottle of water” than “water bottle” in the US

this “reads from left to right” really doesn’t hold up

at least 3

moderated by deletor

that’s why it’s almost as shitty as TV now

my expectations were really low for this one, but it still exceeded them

K, not degrees K

ln -s /dev/null /dev/nul
ln -s /dev/nul /dev/shhhhh
ln -s /dev/shhhh /dev/shhhhh
ln -s /dev/shhh /dev/shhhh
ln -s /dev/shh /dev/shhh

deleted by creator

How did Python end us as Phlegm? It’s one of the chillest languages to write, definitely blood

> Welp, that precisely recreated it -- even identical shas! Looking at
> the b4 output, I do see a suspicious "39 commits" listed for some reason.

Well, that's the point where the user, in theory, goes "this is weird, why is
it 39 commits," and does Ctrl-C, but I'm happy to accept blame here -- we
should be more careful with this operation and bail out whenever we recognize
that something has gone wrong. To begin with, we'll output a listing of all
the commits that will be rewritten, just to make it more obvious when things
are about to go wrong.

> So, I assume the "git-filter-repo" invocation is what mangled it. I will
> try to dig into what b4 actually asked it to do in the morning...

Thanks for looking into this. Linus, this is accurate and I am 100% convinced
that there was no malicious intent. My apologies for being part of the mess
through the tooling.

I will reinstate Kees's account so he can resume his work.

-K

Repo: https://github.com/IRS-Public/direct-file

I change them all to bind mounts. Managed volumes is where data goes to die, if it’s not in my file tree I’ll forget it.