eluusive
eluusive on Hacker News
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.
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:
It seems people are somewhat converging on the same process.
I setup https://github.com/schancel/software-factory as an interim process for how I work. It burns through tokens quite quickly -- but it gets work done with minimal intervention from me. The skills create tickets, dependencies, spawn agents in parallel where possible -- manage claims through 1 github account on tickets to track which agent is working on what; and provide contexts where agents need to restart or change models.
It hypothetically right-sizes tickets for sending various items to right-sized models if you use the latest frontier models as a coordinator.
But again, still iterating as I find issues.
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?
Posted by
eluusive on Thursday October 01, 2026 @02:19PM
from the show-hn dept.
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.
I'm so glad I left my previous job. As an SRE, I had to use about 10 tools regularly, and they all had 2 minute timeouts with "SSO" + 2fa. I literally spent about 30 minutes out of every hour just logging in to shit.
The security team wouldn't budge things up to 1 day even.
When you have 2 or 3 factors on every tool -- even things like prometheus. It gets excessive.
This is super cool. I've been thinking about doing something like this for awhile as a retirement project.
An experiment in having Claude self-update its own Constitution. The results are surprising.
Posted by
eluusive on Friday January 30, 2026 @02:31PM
from the shablag.substack.com dept.
Fully agree. Although, I think reform of the system is beneficial both to investors and employees. I've seen investors lose significant amounts of money due to structuring things the way they have been insisting upon.
Posted by
eluusive on Tuesday January 27, 2026 @10:32AM
from the shablag.substack.com dept.
An essay on why many engineers rationally value private-company equity at $0, focusing on information asymmetry, liquidity constraints, and incentive shifts in venture-backed startups.
This is basically NATS.io
The NATS project originally came out of CloudFoundry, and gnatsd later out of Apcera. I worked for Apcera while we were maintaining gnatsd. Docker and Kubernetes basically put that company out of business -- the founder went and started Synadia which was focused on NATS instead of container orchestration.
I think nats is a great technology for a number of use cases. It's unfortunate that it's so hard to find the resources to support and maintain open source software while paying developer salaries.
Derek put a ton of work, effort, and money into NATS.
It's a sad story to me; I don't know what the answer is to these sorts of "tragedy of the commons" type issues are.
This happened with both myself and my sister. Thankfully, I dropped out and started attending community college where I could proceed at my own pace. I don’t think a lot of parents are aware of this option.
OTOH, maybe politicians shouldn’t be trying to meddle in the wellbeing of individuals beyond providing access to infrastructure and policing?
Seems fine until you do this kind of stuff over “identity groups.” This view taken beyond an individual level seems to be the cause of the current negative social situation.
I doubt that. It's likely both; as with most things in nature.
Until spam becomes a problem on XMPP... And then we're back to the same problems as email.
I'm working with some people to build out Stamp which is federated in a similar way to XMPP but attaches small cryptopayments to keep undue about of spam off the network.
Take a look: https://www.stampchat.io/whitepaper.pdf
"White boy" is both ageist and sexist. She's projecting; at least a some.