danishanish

If most of their revenue was fraudulent it doesn’t prove anything. I’m not saying it’s proof against, but it’s definitely not proof for, either.

I mean, surely when quality is accounted for the difference is significantly higher

Your most recent comment is “This.”

I don’t imagine a model capable of the first part would require being told not to assume a decipherment is correct

It is such a colossal self-report (when meant).

At least there’s positives there…

It’s not blunting a tool, it’s sheathing it. Modern software requires too much proxied trust for this attitude to work.

I think I’m missing something. Financially, what bag would the memory makers be holding here? I don’t think I’m well informed regarding how these deals were structured.

I think it saves labor and eventual bug hunting to include these in a stdlib. We should not be expected to look up the UUIDv4 spec and make sure you’re following it correctly. This feels like exactly what reasonable encapsulation should be.