Ask HN: Will software still matter when AI write all our programs?

Ask HN: Will software still matter when AI write all our programs?

I’ve often reflected on how AI will change software development, and on what happens when reverse engineering — “everything is open source if you can reverse engineer it” — or clean-room reverse engineering, and porting a program from platform A to platform B, become essentially automatic processes.

Personally, this is a capability that would impress me quite a bit. I’m curious to know: if you let something like Astra 6 or Fable run with $10 million worth of tokens, how close could we get to a successful implementation and performance — say, porting the Adobe suite to Linux, or even FreeBSD, or whatever operating system you happen to use? Personally, I think this would be a very interesting benchmark...

And this is where I’d like to get to: why Linux or FreeBSD? If we had this ability to port software, then in many respects the platform, as we know it, would become irrelevant, just like the programs that run on it. The code becomes irrelevant.

You could simply say:

“Create an operating system from scratch, absolutely optimized for my CPU, GPU, and so on, that works and looks exactly like Windows XP — in terms of its interface and workflow. Not only that: take all the dozens of programs I use on Windows XP, clean-room reverse engineer them, and recreate their workflows and behavior, producing versions of those programs for this new platform that you just created specifically for me.”

In this scenario, the code itself doesn’t really matter. The code is almost beside the point. What matters is the specification of how the program is supposed to behave: “If I enter command X, the program does Y. If I click here, a pop-up appears. If I drag this object there, it behaves like this.” And so on. What you ultimately need is not the original code, but a sufficiently complete description of the behavior the code is meant to produce.

Which, incidentally, is the challenge users face when migrating between platforms. The challenge is rarely “Oh, it’s impossible to find a program that performs function X on platform Y,” but rather: “It’s impossible to find a program that performs function X on platform Y in the same way that it performed that function X on platform Z,” not that unlike the concept of technical debt.

In practice, what we would be witnessing is a separation, a divorce between “code” and the “behavior” that the software is supposed to exhibit. People talk a lot about “software as a service”; well, I like to think of this as “software as behavior.” Your “real OS” would be the LLM equivalent embedded into the operating system, functioning as a kind of “program capable of creating programs.” That’s where things get really interesting. It seems that the only piece of software that would truly matter would be the AI running on top of the system.

Acting as a kind of universal translation layer between intent/behavior and implementation. In that sense, perhaps the true “operating system” is less the kernel and more this ability to turn specifications into executable programs.

I’ve been paying attention to these so-called “Agentic OSs,” such as Omarchy, and it seems to me to be heading in the right direction toward what the future of computing might look like. Because, assuming the model is good enough, it could create or port whatever software you wanted. In this scenario, the operating system ceases to be exactly the platform on which programs are developed and instead becomes almost an accessory to the AI.

And at the end of the day, “implementation documentation becomes the source code” — and you, theoretically, setting aside the problem of resources, can always produce that documentation; there has always been enough information to reconstruct a large part of the idea behind the original concept.

--------------------

Anyway, sorry for this long text, probably nobody will read XD But I'm really fascinating by all theses possibilities. I would love to hear your takes.

Discussion 1 comments · 1 points · estranhosidade · 15d
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.

    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 next story in the same article-reader applet. Back returns to the previous story.
    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 Next story link reads on 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, 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.