←back to thread

224 points azhenley | 1 comments | | HN request time: 0.2s | source
Show context
athrowaway3z ◴[] No.45076822[source]
I don't see the case for, what IMO is, more complexity by creating a virtual machine.

We have user accounts, Read/Write/Exec for User/Groups. Read can grant access tokens which solves temporary+remote requirements. Every other capabilities model can be defined in those terms.

I'd much rather see a simplification of the tools already available, then re-inventing another abstract machine / protocol.

I hope we'll eventually get a fundamental shift in the approach to software as a whole. Currently, everybody is still experimenting with building more new stuff, but it is also a great opportunity to re-evaluate and, at acceptable cost, try to strip out all the cruft and reduce something to its simplest form.

For example - I found an MCP server I liked. Told Claude to remove all the mcp stuff and put it into a CLI. Now I can just call that tool (without paying the context cost). Took me 10 minutes. I doubt, Claude is smart enough to build it back in without heavy guidance.

replies(5): >>45076903 #>>45076940 #>>45077041 #>>45077538 #>>45077773 #
1. CuriouslyC ◴[] No.45077041[source]
Virtual machines contain the blast radius. A good agent will be able to take advantage of zero days from within your system to crack you no problem, being a user makes this really easy. You'd have to carefully firewall its knowledge, but there are so many ways to get stuff on the internet (i.e. ask to download an encrypted version of the file in an obfuscated way from a service that can get past the gatekeeper AI). These things are going to be scary good at cracking systems, trust me, you are going to want things to be ironclad.