194
If open weight models are the future, U.S. AI companies are going to have a hard time
(www.fastcompany.com)
this post was submitted on 26 Jul 2026
194 points (98.5% liked)
Technology
86649 readers
2789 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The other problem is bandwidth. Even if you can run Kimi K3 locally, AI usage patterns tend to be very bursty. Having the scalability of cloud compute to run multiple agents and sessions at once makes it much more usable.
My current workflow is passing a human written spec to an agent to implement with strict coding guidelines, architectural decisions, etc. The agent isn't making any decisions about the abstractions to use, it's just creating the objects and test suites. So I don't mind the slower bandwidth because I'm running the heavy agentic lifting over night with no need for human supervision.
But I fully appreciate that my workflow isn't the norm. In fact my workflow it's the exact opposite the AI grifters like Sam Altman are selling because it still involves a human with knowledge of the systems making different decisions.
If you're running stuff overnight on a homelab, you can get away with using very large models as agents in CPU RAM.
Another option is a hybrid approach: farm "dumb" privacy-insensitive calls to an API you can subscribe to for like $40 a year, and let your local LLM do the orchestrating. This is what I do: I run MiMo locally, but also farm calls out to the exact same LLM when appropriate... And I don't mind one bit. I'm happy to pay them back for open sourcing it in the first place.