Mapping agent concepts to the Unix environment sounds like a great idea in general, but I get off the train at adopting the FHS, which is an ancient relic that has no place in a green-field system. I don't know exactly what shape it should take, but something along the lines of Nix seems more appropriate. Or maybe Plan 9.
One reasonably effective defense: "Okay, let me call you right back." Yes, there's always the whole "my phone is dead, I borrowed someone else's" or "I'm calling from a jail payphone", so I think it might become common practice to start making authentication phrases or "tell me something only we know".
Another pillar of basic trust that's being eroded on an industrial scale. Sigh.
How many lines of code is Node, which is a wrapper for v8? I'm aware bun is not great quality, I tried and abandoned it myself, but Andrew's consistently bitter and spiteful tone makes him the worst conveyor of his own message.
> To me it reads like Bun was forked. Will the Zig version survive? Will the Rust one? Both? All options ok.
Maintenance of the zig code was abandoned, while the port continued in the same repo, and it's unlikely any work on the zig branch will keep momentum. So yes it forked, but more in the fork+exec sense (or maybe just exec, the analogy's not that great).
I'm interested less in getting to Elm 1.0 than getting past Elm 0.19, which is the version that locked out all native modules that weren't officially blessed by Elm's author. Far as I can tell, that pretty well marked the end of Elm.
You don't have to learn much resource jargon for a quadlet, just the Pod type, and a relatively small subset of it at that (you're not going to be using things like selectors or priority classes). And there's a script that can convert a compose file to a quadlet, so you don't have to do it from scratch.
> Personally I wish docker had not rejected composition/integration around systemd. Would have made everyone’s job a lot easier in the long term.
It also would have only run on Linux hosts (and not all of those at that), so something else would have been adopted instead. Docker didn't win by being superior to every alternative, it won by being good enough and being everywhere. For portable orchestration, Desktop does ship with kubernetes that's literally one click to enable.
> I wonder if podman would be a speed downgrade here?
Doubtful. But for sure it would be a compatibility downgrade. When I tried podman-compose a couple years ago, I found it nowhere near usable, though I'm told it's improved since. If you want a better Docker for mac, you're looking for OrbStack.
On macOS, there's Orbstack, which is ridiculously compatible (I believe it's based on the same moby engine underneath). On Linux there's oodles of options for working with OCI containers, but nothing else I know of that's compatible with the docker API or CLI.
> What exactly is dangerous about this climb? What kills people specifically?
Lack of oxygen, mostly. Bad in itself, but if the temperatures drop to dangerous lows, you're less likely to notice because you're out also of your head due to hypoxia/hypercapnia.
Perhaps, but I don't see the costs getting anywhere near being worth it. You'd need a space elevator or to manufacture the sinks IN SPAA— er, in space. The latter is theoretically possible but still extremely remote, the former still requires unobtanium.
Train-in-a-vacuum-tube isn't even restricted by the laws of physics, and it doesn't have to be a perfect vacuum anyway, just low pressure. Data Centers IN SPAAAAAACE have the teensy little problem of cooling that you can't just brute-force a solution to. Those giant things dangling off the ISS that make up most of its footprint aren't solar panels, they're heatsinks, and they still have issues managing heat.
The "bully pulpit" of an advice columnist whose main distribution platform was The Onion is somewhat less prominent than that of a sitting United States Senator. I'll just leave it there.
> It seems rude, unethical, puerile even, to do this name-calling and dragging through the mud, if you will, and it was perpetrated/spearheaded, so to speak, by a journalist whose morals and platform encouraged that sort of tactic.
Dan Savage would howl with laughter at the notion of being called a journalist. The morals and platform of the target did most of the work.
Perhaps sports are a net benefit overall, but these are multi-billion-euro companies who don't deserve to keep getting handouts and special favors from the government to supply it.
Good point, though I'll try to draw a distinction between those and subjective-opinion-based slogans like "YAGNI". Maybe I should just limit it to that one: YAGNYAGNI?
Yes, but you shouldn't structure for a future that isn't likely to actually happen. And if you keep things reasonably modular in general, it shouldn't be a major lift to refactor if that future does arrive. Still, Beck didn't do a very good job convincing me. And if you have to always explain what "Real" Blub is and how almost no one practices Real Blub, then maybe Blub was just never a good maxim to begin with.
I have regularly watched agents forget to update one duplicated pattern after changing it somewhere else. If it's within a single file or related class, it'll catch it, but if it's off in some other package in the monorepo, it's a crapshoot.
Speaking as someone who loved the hell out of the dysfunctional mess that was Commodore, and read every Compute's Gazette front to back as soon as it came out: FFS, just let them stay dead. I'm really sick of seeing my generation being strip-mined nonstop for nostalgia.