456 karma · joined September 26, 2022
If you need the sandboxing capabilities provided by the application and don’t want to run it on the host, you should set up a VM, not a container.
From a systems perspective, it’s foolish to rely on a proprietary application to provide its own isolation guarantees. This is an OS-layer responsibility.
ML/AI experts suffer badly from hubris. They are brilliant in one domain. It transfers poorly to systems engineering. The proof is in the FelonyBench results.
It is a marketing expense. We are talking about it. Surely the token cost was worthwhile on that basis alone. Students will likely get some usage out of it, too. But paying a human to do this port would have been an insane thing to do two years ago. I’d be surprised if they have more than 1000 MAUs for this client by the end of the year.
But the MacOS support at this point is pretty atrocious. I mean, it technically runs, but the OS is clearly designed in a way that ruins performance on this hardware. It’ll run Vim, sure, for 2 hours on battery, hot as hell. At this point, Intel Macs are only fine for running Linux.
AWS and friends are very good at providing excellent enterprise grade security, but it’s literal child’s play for nation state threat actors to exfil these models.
TEMPEST / EMSEC alone is a wide open door for unclassified datacenters when the Mossad’s out to get you.
There is absolutely no good reason to burn coal for electricity or heat in this day and age. If we had sane global leadership, every coal power plant left would be treated as a WMD and be bombed harder than that Iranian fuel depot.
It’s not the typical misunderstanding of non-ionizing radiation. The variable symptoms make a lot of sense, given that the weapon is basically just causing random electrical “failures” in the body. This was not a precision op. They saturated a location with this engineered interference signal, with the goal of maiming the target. No regard to whether their families and children would be collateral damage. It’s a war crime on multiple levels, on our soil. Then we presumably went and did the same thing during the Maduro raid at scale.
Just what we needed in 2026, more man-made horrors beyond our comprehension.
Lots of similar reports came out during the Maduro raid. Same symptoms. Seems we demonstrated the capabilities we were hiding. OSINT experts already put the pieces together a month ago. So did our adversaries. Cat’s out of the bag, so no sense continuing to gaslight our wounded veterans.
We probably put this fucking thing in a plane instead of a backpack. Everything’s bigger in the USA, of course.
There are cases where I've staged commits this way for a PR, to make it more reviewable. I'd usually rather split them off into separate PRs, but when that would create a pipeline of three MRs that are meaningless on their own, then rewriting history for a single MR makes sense. I generally consider my feature branch's commit history to be for me, not for you. Going back and rewriting history is a chore that shouldn't be necessary if I did a decent enough job with the PR description and task decomposition. Those commits are getting squashed anyway. Along with all the "fix MR comments" commits on top of it.
It wouldn't bother me to adopt your workflow if it fits your team and its tools and processes. I'd just say, consider that your way isn't the only correct way of doing things. Your preferences are valid, but so are others'. The only thing that really bothers me is absolutism. "My way or the highway."
Your writing here reminded me of a particularly unpleasant coworker I had in the past. I quickly browsed your comment history to make sure you're not him... Excessive rigidity is not an endearing quality.
All that being said, I have also been constantly annoyed by people with too many YoE who can't be bothered to spend an hour or three to learn the basics of how the Git tree is structured, and what merge vs rebase does. They rely too heavily on their GUI crutches and can't fix anything once it goes sideways. Even when you lead them to water, sending them reading material and offering to answer questions after, they refuse to drink. Willful ignorance is far more irritating than stubbornness. I don't expect them to be able to remember what bisect vs cherry-pick does. Claude will spit out the subcommands for them if they can describe what they need in English. But they can't do that if they have no understanding of the underlying data structures...
It’s truly unbelievable that OpenAI and Anthropic were so sloppy. Pirating all that copyrighted media and not even bothering to hide behind one layer of indirection. Amateurs.
So yeah… it’s what, five years’ worth of pent up demand for organized crime, hitting the market everywhere all at once? I’m surprised the request volume isn’t higher!
Of course all the logs can’t be streamed to a terminal. Why would they need to be? Every logging system out there allows multiple stream handlers with different configurations.
Do whatever reasonable defaults you think make sense for the TUI (with some basic configuration). But then I should also be able to give Claude-code a file descriptor and a different set of config optios, and you can stream all the logs there. Then I can vibe-code whatever view filter I want on top of that, or heck, have a SLM sub-agent filter it all for me.
I could do this myself with some proxy / packet capture nonsense, but then you’d just move fast and break my things again.
I’m also constantly frustrated by the fancier models making wrong assumptions in brownfield projects and creating a big mess instead of asking me follow-up questions. Opus is like the world’s shittiest intern… I think a lot of that is upstream of you, but certainly not all of it. There could be a config option to vary the system prompt to encourage more elicitation.
I love the product you’ve built, so all due respect there, but I also know the stench of enshittification when I smell it. You’re programmers, you know how logging is supposed to work. You know MCP has provided a lot of these basic primitives and they’re deliberately absent from claude code. We’ve all seen a product get ratfucked internally by a product manager who copied the playbook of how Prabhakar Raghavan ruined google search.
The open source community is behind at the moment, but they’ll catch up fast. Open always beats closed in the long run. Just look at OpenAI’s fall into disgrace.
Probably a lot of CSAM, if the Mossad blackmail op theory of Epstein is true.
EVs are inherently pretty simple machines. All the complexity is in the battery, and China’s crushing everyone at battery tech. It’s not even close. It’s like a human trying to beat a polar bear in hand to hand combat.
They really need to deregulate the auto industry and let us buy the Yugos with a Jetsons battery. America is a poor country now. Nobody can afford used cars in this economy, never mind new ones.
And you know, I’m already compromising here, because it really ought to be a wagon instead of a van, if Detroit had any brains left.
Can’t wait until someone figures out how to smuggle those $15k BYDs in from Mexico. The North American car market needs to be disrupted badly. By China, not by some meme stock.
That’s damn good customer service right there, if you ask me. The fake-chipper act makes me want to dive into a wood chipper…