The AI Conundrum: We are living in highly subsidized, interesting times

The AI Conundrum: We are living in highly subsidized, interesting times

If you trace the timeline of how LLMs went from a technologist's dream to early text-generation toys, to the world-shifting launch of ChatGPT, and finally to the daily drivers of modern programming (Sonnet, Opus), it has taken less than a decade. It’s a thrilling, almost unbelievable tale.

Let's look at how we got here, and the wall the industry is currently hitting.

- The Dream Phase (2010-2016). By the dawn of the last decade (2011), an interesting thing was happening. The two platforms, Wikipedia and Stack Overflow, had started gaining tremendous traction, folks were collaborating on these platforms to openly exchange knowledge. Looking back, this feels like a more ideal, community-driven path for humanity — one we abandoned for the centralized architecture we have today.

- The Disruption Phase (2016-2021). A perfect storm of unrelated events paved the way for AI. By 2017, new programmers were growing deeply frustrated by Stack Overflow's rigid policies, subjective question rejections, and senior coder pedantry. In retrospect, those strict moderators carved the first stones of what would later become Copilot and ChatGPT. If the community won't answer a beginner's question without downvoting it, a private LLM gladly will.

Add to this Google's landmark 2017 paper "Attention Is All You Need" which unlocked the Transformer architecture, and the forced isolation of COVID-19 in 2020. The ground was suddenly fertile for virtual assistants that could act as isolated developers' programming partners.

- The Hook Phase (2023-2025). The launch of ChatGPT left no doubt about how easy the "hook" would be. For non-technical folks, it was pure magic. It didn't take long for specialized LLMs like Copilot, Claude and Deepseek to become an indispensable part of the programmer's toolbox. Meanwhile, OpenAI was still advertising its "non-profit" roots, and the consensus was that this was purely about empowering humanity.

- The Endgame Phase (2025-present/future). AI companies had miscalculated a lot of things by this time. They were optimizing for the "long-term" but as John Maynard Keynes rightly said many years ago, "In the long-term, we are all dead". The VCs are losing patience today because while the technology itself has gained massive ubiquity and appreciation, the revenues aren't coming as fast. The hook had sort of worked but failed to fully work.

Most frontier models like Sonnet, Opus and GPT 5.5 are still running on 'subsidized mode'. The amount of monthly subscription they charge users (USD 10/20/30 per month) is a pittance compared to all the compute and RAM needed to run those "thinking..." and "pondering..." tokens. In order to truly show profits in the books and come out of subsidized mode, they must charge on the scaling of input/output tokens and that appears to be difficult. Very few companies might be able to sustain such unlimited budget for unpredictable hardware scaling, the recent Uber story shows exactly what happens when they try doing this.

The frontier models are trying to replace something which could never be successfully delegated or automated in entire human history - the highest cognitive skills of human brain like reasoning, deduction and logic. Yet, the efforts are on and the goals are long term. The conundrum is that if they stop subsidizing, the hook phase may be undone - there is a strong possibility of folks reverting back to older ways of Wikipedia/Stack Overflow or pivot entirely to open source dry/academic models like Llama and Qwen which can run locally on their own hardware. And yet, they also can't keep subsidizing and draining the funds indefinitely.

What happens when the subsidy mirror cracks?

Discussion 1 comments · 10 points · pyeri · 2026-06-21
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.