Steve bannon figured this out a while back. I was reading about it in the Epstein files in a discussion between the two of them. If they can keep the average person dizzy with bad news they can do more bad things easily. Cute trick

I've always been impressed by Amazon's ability to present the shittiest experience possible and imply the blame is with things like isolation that they don't really provide.

That is going right back to false dichotomy. Something can be meaningful and not clean up the streets of all things uncomfortable.

Sure, but if it doesn't specifically solve the problem of cleaning up the streets of visibly-homeless people, then it doesn't solve the problem of public transit authorities wanting to remove benches from public transit waiting areas.

I like nix and its approach but if I'm being honest I think its also getting easier to be sloppy about dependencies and ask AI to find any dependencies that might be missing from the cleanly installed packaging metadata. There's maybe a paradox for developers in that we can try to drop structure and brute force scan first intensively enough to catch anything likely to get caught or we can ask AI to finally apply all the rigorous methods we decided were too expensive for routine software and probably have minimally more things to run with each release.

The standard for pretty much any multiuser app of a reasonable size is a quorum of SQL or noSQL DBs preferably as a single source of truth for all retainable state. Personally, I think foundationDB is the closest to an attempt to make the minimal viable base layer that I've encountered. But C/C++ based and then owned by apple make it not suitable for the role.

It's a liability to businesses not to know who may physically be in Utah so they should probably ban together to exclude Utah from all networks. I.e. ISPs caught dealing with Utah should have their peering revoked.

I don't think it was a bad idea, doing any idea requires an investment and a better investment would have been kernel layer, just ask the history of export control law what the US feared breaking more. Having security in userland means attacks in kernel or in userland are worthwhile against it. In the kernel it could have been secured better than OpenSSL was with less resources and could have had keys unavailable from userland. Instead it got basically no uptake as everyone hobbled along on slightly more resources spread even thinner on OpenSSL clones.

What would adding your own canaries achieve? They know the channel that is leaking from any canary you can't remove.

To dilute the list and add more to confusion, court hardly will accept it, in this case, they won’t be able to shut it down since it has other bogus entries.

If they create a system to compensate expert AI users wouldn't that career have a problem in that anyone (enticed by the new careers existence and) integrating their advice on any company particulars with a (weeks) more modern approach is basically putting them in the role of domain expert being eliminated.

The part I push back on is the idea that expertise is easy to learn in just a few weeks.

Take Andrej Karpathy as an example. Even if I knew exactly what tools he uses and what his workflow looks like, I still would not be able to produce anything close to what he can produce in a few weeks. And he is not standing still either—he is evolving at the same time.

A lot of real expertise is not in the visible/system-able workflow. It is in someone’s experience, taste, judgment, and wisdom. You can copy the artifact, but you cannot easily copy the thinking behind it: the principles, the decision-making, and the ability to apply those principles across many different/subtle situations.

But I do agree with the concern behind the argument. People may worry that sharing what they know could weaken their own position. And the more uncomfortable question is about peers: if someone’s role can be “retired” because others absorbed their knowledge and skills, then it is hard not to ask, “Am I next?”

Sure but here you are not talking about the 100000+ local firm experts for windows networking or coding with agents you are talking about the people who can rewrite the best advice that makes those local experts out of date where their small experiences probably don't make up for not having integrated X, Y or Z yet.

The TUIs I've looked at seem to be largely NPM dependent? Bizarre that agents apparently don't have time to rewrite themselves in something that isn't a security tire fire. It kind of makes me assume that all this agents taking over stuff is from people working at garbage-pivot-garbage startups that don't really have to worry about any consequences but not being fast enough.

99% of LLM-adjacent software is webslop in a state of perpetually broken churn.

OpenCode for example has not yet figured out "maintain a log of all messages and send that log to the SSE endpoint in the same order to get the next response" and has regular prompt cache misses even with context pruning disabled

Go + Lipgloss + Bubbletea is by far the most robust and performant stack for building (and or generating) aesthetic and usable TUIs. Excellent DX. No npm necessary

Is the Go ecosystem really that much better? As an outsider it looks like there's a fair amount of library use, more than I'd like.

Check out the Crush agent harness. It's very impressive.

Impressively many dependencies? I estimate about 75-125 in the dependency tree, including multiple versions of the same package. Now compare to something written in e.g. C: such a program might have 2 dependencies: libcurl and ncurses.

Yeah that’s the thing, pretty much all the people who are really into ai for everything are JavaScript/Typescript developers, usually working at startups, and often in the AI field.

AI is only good at the work I'm not paid to do

Return to the halcyon security era of curl piped into bash