News for hackers. Stuff that matters.
Re:Goldman Sachs Is Pulling Claude Code from Its Bankers and... by hobofan on Monday November 09, 2026 @04:30AM (#50423215)
Of course you loose quite a bit intelligence that way, but if you use a local model (and for many actions a decision model), which can run on a lot of office workers hardware nowadays, you can just run everything locally: local model, local code interpreter sandbox, local file access.

If you don't send the data anywhere remotely (by using a local model, and restricting web access of the sandbox), you don't have to worry about exfiltration of sensitive contents of files, which heavily reduces the allowance prompts for the user.

Obviously that's not in the interest of OpenAI/Anthropic, who are the main providers of "general office work" desktop tools like Cowork.

Re:Goldman Sachs Is Pulling Claude Code from Its Bankers and... by cheesecakegood on Monday November 09, 2026 @10:43AM (#50427136)
That’s two replies in a row from two different users, with the same mistake and I feel obligated to let you know that it’s “lose”, not “loose”. Lose is the opposite of win, but also no longer having something you previously possessed. Loose is the opposite of tight, or being relaxed or casual about something. They are also pronounced differently.
Re:Goldman Sachs Is Pulling Claude Code from Its Bankers and... by billdueber on Monday November 09, 2026 @03:17PM (#50431352)
“Loose” instead of “lose” is all over this site like a bad rash. I’m fascinated by it, because in general, the writing here tends to be of a higher quality that I find on many other sites. This mistake, and the use of incorrect prepositions, seems to be more prevalent among higher than average quality writers than other similar mistakes. I’d love to know why!
Re:Goldman Sachs Is Pulling Claude Code from Its Bankers and... by hobofan on Monday November 09, 2026 @05:07PM (#50432951)
A big chunk of this website is ESL. Unless you are listening closely, "loose" and "lose" sound almost exactly the same (especially in regards to the length of pronunciation of the "o"), which for ESL speakers like me can make it hard to derive the spelling from the phonetics.

In the end, it's also just a typo.

Re:Goldman Sachs Is Pulling Claude Code from Its Bankers and... by dingdongditchme on Tuesday November 10, 2026 @10:36PM (#50449495)
close, hose, pose, froze.

noose, goose, smooth, tooth,

Re:Goldman Sachs Is Pulling Claude Code from Its Bankers and... by NichoPaolucci on Tuesday November 10, 2026 @01:22AM (#50436758)
I was going to say the same! I've seen it frequently enough on here that I started to think I was going crazy. For a site that generally has few typos + relatively in depth technical writing, it's definitely intriguing.
Re:Goldman Sachs Is Pulling Claude Code from Its Bankers and... by dingdongditchme on Tuesday November 10, 2026 @10:32PM (#50449471)
Former colleagues and I have noticed that we each have a muscle-memory type of typo that we would make repeatedly "just because". For me some of those stem from being bilingual. One of these was my phd advisor, arguably the smartest person i've met. Lose is too close to hose which makes no sense from a pronunciation perspective. So it should be loose which sounds more snooze or smooth.
Re:Goldman Sachs Is Pulling Claude Code from Its Bankers and... by hobofan on Monday November 09, 2026 @04:58PM (#50432842)
It's a typo. Get over it.
Re:Goldman Sachs Is Pulling Claude Code from Its Bankers and... by dingdongditchme on Tuesday November 10, 2026 @10:23PM (#50449421)
Is it a typo or a hidden signal that I am not a bot... we will never know.