In my opinion, training through embodiment and constructing an internal world model makes it possible to do genuine reasoning about how objects behave in the physical world. We have a continuous feedback loop where we take an action, and see the result giving basis to our shared context we lean on when communicating with each other. Having context is key for being able to explain why you made a particular decision, and allows for error correction and guidance towards better decisions through conversation. This is largely what we mean by having understanding in a human sense. So, having a world model in the context of robotics is the most likely path towards creating a genuine artificial intelligence.
Same, I've got a Pixel 9 and GrapheneOS works perfectly on it. I really love having full control over the OS on my phone and being able to decide what actually runs on it.
Amazon has a ton of internal politics just like any other large organization. It's entirely possible there's a faction that is trying to kneecap another faction within Amazon with this.
I expect the blast radius will include every American service provider. The problem isn't exclusive to Anthropic, the same thing could happen with OpenAI tomorrow. Using American platforms is a huge business risk now and there's no putting toothpaste back in the tube here.
This is the first time the US decided to unilaterally cut people around the world off from American AI services with zero notice. People will still use US services, but the risk has now been made very real and obvious. Believe it or not companies do price in risk.
You absolutely can have the LLM write maintainable code. A few tricks I use are to ask it to plan out features in phases, and then do a branch and a PR for each focused piece of work. It makes it a lot easier to review and understand what's happening.
I also ended up making a tool which lets the LLM get a high level perspective of the codebase, and then see parts that are structurally gnarly. I've been using it to do refactors and clean things up periodically. It helped a lot with keeping the architecture clean.
There are two parts to this too. One is the raw model capability and the other is how well the harness guides the model and meets its expectations. I really think for stuff like agentic coding, this has to be treated as a package. This is my favorite example of how much difference a harness can make even for a tiny model https://github.com/itigges22/ATLAS
And you're bang on with the storage comparison, we're basically in the mainframe era of this tech, but there's no reason to think that it won't get optimized to the point where you can run the equivalent of current frontier locally.
reply