> Even if you RAID them, there's not a good way to move that VM to another host if there's a RAM or CPU or other hardware issue on that host.
This is the critical point. All hardware fails eventually. The CPU and RAM are, in a real sense, also ephemeral. The only relevant question is what the risk tolerance of the use-case is. If restoring from async backup is sufficient, then embrace ephemerality and keep backups. If you need round-the-clock availability, pick an architecture that lets you fall over gracefully to another machine, and embrace the ephemerality when you inevitably need to do so.
Quite the opposite: retirees will flee to low cost of living areas, taking the money that they spend in other sectors (food, health, entertainment, etc.) elsewhere.
There's multiple tools that generate architecture diagrams from text/code (Mermaid, LikeC4...). You start using one and tell the model to generate the text for the architecture diagram and it'll do it. Stuff like https://erode.dev tries to use LLMs to keep it in sync.
Spec-mode in the Kiro IDE generates requirements and design docs for a feature; the design always contains one or more Mermaid diagrams of the arch in the feature.
Considering that people expect literally the same thing, I can understand how even small regional differences can seem extreme. Like not finding any beef on the menu in India, or any bacon in the Middle East.
Your point isn't contrary to LLMs or LLM-powered robotics. LLMs have access to the entire human corpus, including documented regional specializations, as you describe. The LLM knows via sensors where it is and what local conditions are. The LLM could even hypothetically conduct experiments to try to find further hyper-local specializations, instead of just relying on monocrop agriculture.
It all depends on the agent harness and the system prompts.
> "post capitalist society" was the recognition that capital ceased being the primary factor of production. No matter how much capital you throw at a problem, if you can't retain people that know what you're doing, you won't get far.
This leads to the reformulation of knowledge workers as "human capital", and it's hardly post-capitalist. A capitalist society is one where people assemble different forms of capital to produce capital returns that are larger than the sum of the capital inputs, where the possibilities available to you depend on the amount and quality of capital that you have access to. This is all still very relevant when discussing human capital - access to human capital is determined by the quality of your professional networks, whether you decide to be present in geographic talent clusters (i.e. cities as centers of industry), and whether you have sufficient financial capital available in trade.
AI will not transition us to a post-capitalist society. Its promise is solely the ability to replace human capital with other forms: chips and electricity. It does not spell the death of human labor any more than computers and spreadsheets did for accountants.
Most commenters here: "Mythos is powerful because you can point it at a whole codebase, if you point the smaller models at a whole codebase and iterate through small sections of code, you'll get too many false-positives to handle."
This misses the point entirely. You pay $20k as a one-time fee to establish a baseline. Your codebase develops one PR at a time, which... updates isolated sections of code. Which means you don't need Mythos for a PR, just small, open-weight models. Maybe you run Mythos once a year to ensure that you keep your baseline updated and reduce the risk that the open-weights models missed anything.
Seeing this as anything but a huge win for open-weights models and a huge loss for Anthropic misses the point entirely. Mythos isn't something you can persuade Fortune 500 companies to spend $20k/day or even $20k/week to spend on, like they were hoping for. $20k/year is a lot less valuable, and it won't justify development costs or Anthropic's growth multiple.
Your analysis presumes air power alone. Assets are seized by cavalry (in modernity, APCs and tanks) and held by infantry. Nothing new under the sun.
The only reason anybody is thinking of destroying civilian infrastructure (wealth) is because everybody took off the table the prospect of sending in cavalry and infantry to seize and hold it.
USA rightly hesitates to send in the cavalry & infantry, because there, against much more numerous opponents, it no longer has the crushing advantage that it has in air power.
The chances of success of such an action are very low, unlike for air strikes, as it has already been demonstrated by the failure of the incursion attempted by USA one week ago, which resulted in significant US material loss, e.g. the 2 scuttled transport airplanes.
> here, against much more numerous opponents, it no longer has the crushing advantage that it has in air power
Be careful not to compare absolute sizes of militaries (which matter in a long term, strategic sense) to the number of soldiers deployed to a specific battlefield (which matter in a short term, tactical sense, for that particular battle). Adversaries who deploy large numbers of troops into a small area make them vulnerable (to foreign air power, yes, but mainly artillery). Adversaries like Iran may have staggering military sizes on paper but their ability to deliver significant numbers of troops to a battleground, particularly when roads, airstrips, and paratrooper transports are destroyed first (by air power), is far more limited.
But you're alluding to a separate concern, which is whether the US military has enough manpower for long-term strategic purposes, particularly since we can't do much about the size of adversary militaries before wartime, but can do something about the size of our own.
> significant US military loss, e g. the 2 scuttled transport airplanes
If the loss of two measly planes is ever enough to be a "significant" military loss, then God help us. The military wastes far more, even in peacetime. We should be so lucky that the enemy continues to hurt us less than we hurt ourselves.
The cost of building all the tunnels is astronomical. Making tunnel boring cheap, fast, and resilient to different soil types + rock would also pay huge dividends for urban mass transport (subway lines).
Certainly economically. NIS-USD exchange is now 3.09 and continuing to drop, reflecting optimism.
Strategically, it remains to be seen what will happen to the nuclear material in the peace talks. If Iran emerges from the war with an intact nuclear program due to a lack of American stamina to carry through and achieve its war goals, that would be an enormous strategic defeat for Israel.
This is the critical point. All hardware fails eventually. The CPU and RAM are, in a real sense, also ephemeral. The only relevant question is what the risk tolerance of the use-case is. If restoring from async backup is sufficient, then embrace ephemerality and keep backups. If you need round-the-clock availability, pick an architecture that lets you fall over gracefully to another machine, and embrace the ephemerality when you inevitably need to do so.
reply