Comment by YeGoblynQueenne

Comment by YeGoblynQueenne

>> If there happen to have been as many as four humans working on Navier-Stokes at any given time since the year 2000, then that's more human-years applied to the problem than agent-years.

My bad for not showing my work and inadvertently leading you down the garden path, but the "~100 agent-years" calculation goes like this:

10,000 agents * 88 hours = 880,000 agent-hours

88,000 agent-hours / 24 hours = 36,666.7 agent-days

36,666.7 agent-days / 365 days = 100.5 agent-years.

That's what you get for working 24 hours a day, 7 days a week, 365 days a year. Realistically speaking, that's not a work schedule any human can follow.

It's hard to make a realistic estimate because normally even a very dedicated mathematician will not be working exclusively on one problem all their waking time, or even all their working time. But, let's ignore this and assume a pretty standard work schedule of 8 working hours, five working days a week, and 52 working weeks a year.

Now, that's:

8 hours * 5 days = 40 working hours a week

40 hours * 52 weeks a year = 2080 hours a year

880,000 agent-hours / 4 humans = 220,000 hours per human

220,000 hours per human / 2080 hours a year = ~105.8 years

To clarify, that's how I estimate the number of years it would take a mathematician to do a quarter of the work of the 10k OpenAI agents if that mathematician worked only on solving Navier-Stokes and did nothing else in their entire career.

That's just not a realistic work schedule for any human. You can adjust the working hours if you want but I don't believe you'll get any realistic estimate. Don't forget that most academics' careers last around 30 years from PhD to Professor Emeritus. If you want a more realistic estimate of how much time it would take how many humans to do the work of the 10k OpenAI agents, you can start from that assumption and work your way up from that.

>> That would be a more convincing argument if the AIs, like the humans, had been around and trying to solve those problems for the last 2k years. However, as you might have noticed, the state of the art in AI was rather primitive 2000 years ago.

Sure. But the thing is agents can run 24/7, 365/365 in parallel and as you see above they can cover 2000 years of human work in much less time. I'm not going to estimate how much because the only bottleneck is the amount of compute and money that an AI company wishes to spend, and that depends on their motivation to solve a particular problem. However, with sufficient motivation 2k years of human research (keeping mind that's not 2k years of continuous work) can be covered in a few ... months? Probably.

Replies YeGoblynQueenne · 13d
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

    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.

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