eluusive

Meh. This is just structured logging with some post processing. You can definitely derive metrics and traces based on them, but doing so is more expensive in many ways.

I worked at one of the early "container companies"; and wrote large parts of an in house mostly docker-compatible container engine. It was going to be part of a container orchestration platform pre-k8s and docker swarm.

This guy is totally correct. We also used Go for everything -- as it was hot stuff at the time -- and also very frustrating to deal with early version. Dependency management nightmares, bugs in the runtime, etc.

He also had to have a C shim that got loaded first, or shelled out to.

The hype around Google tools was pretty fascinating. I felt like that was the primary reason around using such an immature language at the time. There were better systems languages around for that kind of work.

They're not wrong...

Just switched, and it seems to be much better. I'm hoping it stops lying. I have Pro max subs for Claude, Codex, Grok, and Google AI... I was forced into using Google by running out of credits elsewhere.

I have found that Gemini often claims it did something, but didn't actually complete the task.

I just had 3.8 Flash do a major refactor -- that never should have needed to be done in the first place -- and switched to Argon 4, and had it review it.

Almost everything had been stubbed out by 3.8, and none of it was properly integrated into the codebase. :facepalm:

Who would want to play Gran Turismo without long CD loading screens?

The way passkeys have been implemented is an absolute travesty. If it were one passkey per device, and 2-factor was still being enforced, I'd support them. But

But, instead, we end up with 1 passkey per device (potentially per web browser) per website -- and some websites do not allow any other kind of auth. If you lose that phone, or wipe it, move on, or it is compromised, now you can't login to your account anymore?

There is literally no reason for all of this nonsense.

Websites should be providing a challenge, your device should produce a tweaked key based on the domain, sign the challenge, and that should be it. You have one root key per device.

A standard API to register new passkeys for new devices.

Require two factors Password + passkey, or two passkeys.

No transferring private keys between devices.

Requiring 2 factors per website per user, potentially per device, is far more complexity than most people are capable of dealing with.

And I really do not like that my phone# and email# are now de-facto second factors on everything.

Sounds like if this was incorporated you could include metadata files in crates and even avoid that analysis cost being repeated? Something like typescripts.d.ts files?

Doesn't mean much at the moment. There's not much that supports its architecture.

This is a response to the supreme court ruling on birthright citizenship. They're using the levers they do have, since that was removed. Anyone who agrees with the ruling should really read justice Thomas' dissent.

I can't quite put my finger on it. It doesn't write as well as Sonnet. Also, I feel like it follows instructions much more poorly. I do a lot of iteration on my projects and telling it to follow the same process I just had it do, and it'll deviate or invent something totally different.

I find myself having to check the work much more. It takes quite a few liberties with procedures I wanted it to follow.

Use to work with a pretty jaded Army Colonel. He'd often say: "even periodic motion looks like progress on short enough time scales." And also, "Slow is smooth and smooth is fast."

The new "cloud" UI is wful. Who thought this was a good idea? I hate MacOS Tahoe.

I migrated off Patreon awhile back. It's extremely clunky, and the service charge is pretty high comparatively.