Nov 2024: Don’t dismiss this; it may be the next platform shift. But the actual questions are still unsettled: scaling, usefulness, deployment, and business model.
May 2025: The model layer is already showing signs of commoditization, so the important question shifts toward deployment: products, use cases, UX, errors, and enterprise adoption.
Nov 2025: The capital cycle has become the story: everyone is spending because missing the platform shift is worse than overbuilding, but there is still no clarity on product shape, moats, or value capture. That creates bubble-like dynamics.
May 2026: Provisional thesis: models look likely to become infrastructure, while value probably moves up-stack into apps, workflows, product, proprietary data/context, GTM, and new questions made possible by cheap automation. But he is still explicitly calling this provisional.
Same thing happened on other places the open source offering became popular.
OpenAI / Google / Anthropic / XAI also have a ton of compute. That is the real moat.
It feels great to finally have access to something local.
https://bsky.app/profile/antirez.bsky.social/post/3mlzwmvlov...
It's much closer than you think. We're going to see specialized hardware in the next 24 months capable of running 2025-era frontier models. That's big.
On the technical side, one of the additional things I've had on my mind is the potential that these mega models are in fact hiding a ton of inefficiency.
The approach of simply shoving higher dimensionality and more parameters into largely tweaks to the current models has delivered results, but it feels like "mainframe" era of computing to me.
Throwing reams of annotated human content and forcing the machine to globally draw associations from it feels clumsy. Just as people are able to learn structured knowledge via rule-systems that are successively elaborated with extensions and situational contradictions, I feel like there's probably a much more compact representational model that can be reached by adapting the current technical foundations (transformers, attention, etc.) to work well with generated examples from rule-systems, that then gets used as a base layer to augment the "high level" models that process unstructured data.
The risk for the behemoth datacenter might be similar to the risk in the early computing era of building compute centers right before the PC revolution took off.
If it turns out that there exists some more compact and efficient representation for this intelligence (which IMHO is likely given that we are still in the first generation of this technology), the datacenters may end up decaying mausoleums of old tech that has no relevance to a distributed intelligence future.
That's the big technical unknown unknown for me. How much efficiency juice is there left to squeeze, and what does that mean for a distributed landscape vs a centralized datacenter based landscape.
> "What happened the last time that everything changed?"
Honestly, I'm glad we hear more of the commoditization of AI, and I hope that the comparison of AI with water or electricity will become mainstream and that the states (as in nation states) will understand that sooner rather than later and act accordingly.
* Hardware era (pre 1995s) -> IBM, Intel, Microsoft, Apple
* Internet era (1994-2001) -> Amazon, Google, Meta, Salesforce
* Mobile era (iPhone+ era) -> Uber, Mobile Games, Youtube, Snapchat, Tiktok, Airbnb
* Cloud era (AWS+ era) -> AWS, GCP, Azure, Snowflake, Databricks and bunch of other data & database startups
AI era (ChatGPT+ era) -> Change is inevitable
Change might be inevitable, but I'm not sure your list shows or proves that.
Edit: I hadn't seen the original presentation yet. I see that Evans already divided the eras like I suggest above.
In a way this is like distilling (but it is not) but you can make better harness (tackle more edge cases, better tool/function definitions, sandbox handling, bash management, DB management, deployment management, etc.) but extracting what LLMs know into code.
Maybe I am wrong but I would like to see custom software for the last mile (tiny/small businesses) becoming a reality. AI would eat the world of software but costs would go down since you can extract value upstream from the LLMs and spread downstream through tighter coding agents.
I am building a coding agent that will not be small - it will be a lot of code, carefully mixed roles (mimic a software dev shop) with separate tools available to different roles. And all this code is generated by other coding agents. https://github.com/brainless/nocodo
I am a nobody from nowhere with 18 years of software engineering behind me. I do not care about revenue. I just want to see a regular business owner's workflow going live on their own VPS.
why is it multiplied by 13?
(365/7)/12 = 4.3452…
I'm old so my computer career has gone: punch cards => calculators => command-line => GUI => touch screen => voice => chat. Chat seems to be the best blend of expressiveness and utility, with a dose of magic thrown in.
Models were always going to be the commodity, just like the most popular and viable use cases at present are less job-replacement than "let's analyze huge data sets for patterns we're missing, and adjust accordingly" or "probabilistically generate deterministic software for me for X function/task". One-offs simply aren't profitable when models are interchangeable commodities, hence that brief attempt to pivot to "pay by outcome" before giddily embracing the classic consumption-based-billing playbook.
This is a marketing Gish Gallop talk that pretends to invalidate counterarguments with a couple of fantasy graphs.
And then, if there is any data that you think is incorrect, or arguments that you disagree with, you should explain why. All of the charts are sourced, and none of them are 'fantasies'.
It is very secure to be pro-AI while the rest has to resort to unregistered typewriters like in the Soviet Union.
To quite Ilya Sutskever:
> I think it’s pretty likely the entire surface of the earth will be covered with solar panels and data centers.