Yes, you have to use the same session, I guess you could load up a bunch of context, then fork the session into a few different tasks, although I haven't tried it.
You're implying that the U.S. securities worth hundreds of billions held by a nation will be under threat of theft (by the U.S. government itself?) because the nation doesn't "have bargaining chips"?
So the U.S. will begin to rob and plunder the bank accounts of countries that don't have a bargaining chip?
Is that where the U.S. heading? The daylight roberry of the bank accounts of foreigners?
I'm at an org, where every medium to large company meeting talks about AI in similar breathless non-specific terms, yet m365 copilot is the only approved AI chat, and GH copilot the only AI coding tool.
I relate to the points about obscure platform limits, and leaky abstractions, but when I look at the exe.dev platform, it might be the most obscure PaaS I've seen, and has it's own strange abstractions.
The shell command to start a new vm, has a --prompt flag to get an LLM to configure the VM for you.
VM's have no public ipv4 IP, and the ipv6 IP doesn't seem to allow incoming connections.
The only supported inbound connections are via their HTTP proxy.
There is no private networking.
At first I interpreted the complaint about cloud providers not offering nested-virtualization, as something he intends to address by offering it as a feature, but no, instead he means that exe.dev's VM abstraction eschews the need for it.
Yeah I had a giggle about that also. He argues: “cloud abstractions are the wrong shape”, then what they actually ship is: a different abstraction, with even more hidden constraints.
I'm very curious how they deal with subscription levels/noisy neighbors.
reply