Zach Attack is Back

@awnihannun maybe open source claude models that run on MLX soon!?!!?

I joined Anthropic as a member of the technical staff. Excited to work on frontier modeling at a place with unwavering values and a generational mission.

lol, I broke @Alibaba_Qwen 's brain:

@FrankieAshcroft @flyosity @SecWar thank you grok 🙄

@flyosity @SecWar Here, though, the government isn't compelling Anthropic to rewrite its policies or hand over models under threat of force—it's ending its own business with them, labeling the firm a supply-chain risk, and barring contractors from dealing with it. That's sovereign procurement.

This week, Anthropic delivered a master class in arrogance and betrayal as well as a textbook case of how not to do business with the United States Government or the Pentagon. Our position has never wavered and will never waver: the Department of War must have full, unrestricted access to Anthropic’s models for every LAWFUL purpose in defense of the Republic. Instead, @AnthropicAI and its CEO @DarioAmodei, have chosen duplicity. Cloaked in the sanctimonious rhetoric of “effective altruism,” they have attempted to strong-arm the United States military into submission - a cowardly act of corporate virtue-signaling that places Silicon Valley ideology above American lives. The Terms of Service of Anthropic’s defective altruism will never outweigh the safety, the readiness, or the lives of American troops on the battlefield. Their true objective is unmistakable: to seize veto power over the operational decisions of the United States military. That is unacceptable. As President Trump stated on Truth Social, the Commander-in-Chief and the American people alone will determine the destiny of our armed forces, not unelected tech executives. Anthropic’s stance is fundamentally incompatible with American principles. Their relationship with the United States Armed Forces and the Federal Government has therefore been permanently altered. In conjunction with the President's directive for the Federal Government to cease all use of Anthropic's technology, I am directing the Department of War to designate Anthropic a Supply-Chain Risk to National Security. Effective immediately, no contractor, supplier, or partner that does business with the United States military may conduct any commercial activity with Anthropic. Anthropic will continue to provide the Department of War its services for a period of no more than six months to allow for a seamless transition to a better and more patriotic service. America’s warfighters will never be held hostage by the ideological whims of Big Tech. This decision is final.

are people really this dumb? or is this rage bait?

is it just me or is opus 4.6 kinda worse than 4.5?

@awnihannun My favorite thing to do every morning now is git pull mlx and mlx-lm its like christmas every day

mlx_lm.server + Qwen3 Coder Next 6bit + OpenCode + M3 Ultra = a pretty capable and very fast local coding setup. Not sped up:

This release is an emtional one for me because I had stayed up so much for it 🥹 It has been truly amazing to see this model becomes better bit by bit through every change we make, and we have come a long way. Since I did mid-training for this model, I wanted to share a little anecdote about this part. We really made this model with user experience as first-class consideration. We want people to actually use it, period. We took it so serious that we redid midtraining because we saw cases where models failed to follow instructions on out-of-distribution scaffolds. We decided straight-up that we would fix this in a fundamental way instead of surface-level patching. The resulting base model, which we also release, is thus a healthy base. We find that, compared to other base models, this one better learns new tasks. Try fine-tuning our base and lmk what you think 🥳 huggingface.co/Qwen/Qwen3-Cod…

@brankopetric00 Mistake #1.5 - running services like ssh on standard ports

@everythingnow52 @xavierjp__ Christianly speaking, ur an idiot and an embarrasment to christianity

@xavierjp__ You? No. Truly I hope you find the truth in Jesus and leave that false God of yours. But we both know that's never going to happen. Jesus is Lord. Have fun in hell

If you are a non Muslim, please do not feel obligated or pressured into not eating or drinking in front of us Especially in your own countries If you do decide to not eat in front of us, we would thank you for the kindness, but tell you it’s not necessary And if you decide to go about your day as usual, eating and drinking as you normally would - as is your right - then there is no issue with that Islamically speaking there is no obligation for you to abstain from eating infront of us And we will not have a problem with you if you do so Ramadan is OUR obligation, not yours

Lol. @theo is a junior dev? Shots fired.

Honest question. Are you willing to pay $1500 for this?

@dillon_mulroy git actually already has a really nice way to see which specific changes are associated with some text description not many people know about this! git-scm.com/docs/git-commit

@alexschultz002 @badcop_ @dillon_mulroy People still write commit messages manually? This task was replaced by AI a long time ago.

@badcop_ @dillon_mulroy If only people actually filled out the message with meaningful information. This is one if the reasons why I encourage `git commit` over `git commit -m`

this. something like this please

@badcop_ @dillon_mulroy

@kenwheeler @Enscion25 Genuinely concerned for humanity at this point. I thought political divides were bad, but now we have to explain that LLMs are just computer programs and somehow that brands us insensitive or “virtue signaling” ? This whole situation is in fact insane.

@Enscion25 no, people are ensouled monkeys. they are real. the bot is not real.

This is the thing that always gets me with these virtue signaling cunts such as @theo You have branded a group of people as unwell, you claim that you have some type of care about their mental state . Yet, you screenshot their profile, call them "insane" and then proceed to publicly humiliate them infront of your very large followerbase. Imagine walking down the street, seeing a person having a panic attack, snapping a pic, and then posting it to your followers with the caption "I think this asshole may have anxiety" It's basically the same thing

If a man says he will fix something, he will! There’s no need to remind him every 6 months.

Ok, starting to fall in love with the design of the new forestriverinc.com/rvs/campsite-e… ... @IanBakerRV @CampingWorld When can we get a manufacturing tour of these new 5th wheels!?!?!

@SledgeDev @kenwheeler @theo @theCTO @AnthropicAI @cursor_ai @Apple Said no one ever

@kenwheeler @theo @theCTO @AnthropicAI @cursor_ai @Apple I love Xcode

i think @AnthropicAI should buy @cursor_ai

@dillon_mulroy @BraydenWilmoth And then get out of their way, let them cook and ship. If you pile on protocols, hurdles, multiple review processes, specific release days, that take days/weeks to ship the fix to prod… you will lose those people.

@BraydenWilmoth x.com/jaredpalmer/st…

Cloudflare is built different. Tweet about a problem you have, and chances a developer responds… even fixes it for you… is very very high.

Microservices is the software industry’s most successful confidence scam. It convinces small teams that they are “thinking big” while systematically destroying their ability to move at all. It flatters ambition by weaponizing insecurity: if you’re not running a constellation of services, are you even a real company? Never mind that this architecture was invented to cope with organizational dysfunction at planetary scale. Now it’s being prescribed to teams that still share a Slack channel and a lunch table. Small teams run on shared context. That is their superpower. Everyone can reason end-to-end. Everyone can change anything. Microservices vaporize that advantage on contact. They replace shared understanding with distributed ignorance. No one owns the whole anymore. Everyone owns a shard. The system becomes something that merely happens to the team, rather than something the team actively understands. This isn’t sophistication. It’s abdication. Then comes the operational farce. Each service demands its own pipeline, secrets, alerts, metrics, dashboards, permissions, backups, and rituals of appeasement. You don’t “deploy” anymore—you synchronize a fleet. One bug now requires a multi-service autopsy. A feature release becomes a coordination exercise across artificial borders you invented for no reason. You didn’t simplify your system. You shattered it and called the debris “architecture.” Microservices also lock incompetence in amber. You are forced to define APIs before you understand your own business. Guesses become contracts. Bad ideas become permanent dependencies. Every early mistake metastasizes through the network. In a monolith, wrong thinking is corrected with a refactor. In microservices, wrong thinking becomes infrastructure. You don’t just regret it—you host it, version it, and monitor it. The claim that monoliths don’t scale is one of the dumbest lies in modern engineering folklore. What doesn’t scale is chaos. What doesn’t scale is process cosplay. What doesn’t scale is pretending you’re Netflix while shipping a glorified CRUD app. Monoliths scale just fine when teams have discipline, tests, and restraint. But restraint isn’t fashionable, and boring doesn’t make conference talks. Microservices for small teams is not a technical mistake—it is a philosophical failure. It announces, loudly, that the team does not trust itself to understand its own system. It replaces accountability with protocol and momentum with middleware. You don’t get “future proofing.” You get permanent drag. And by the time you finally earn the scale that might justify this circus, your speed, your clarity, and your product instincts will already be gone.