Comment by PaulHoule

Back to stories Open in a window
Comment

Comment by PaulHoule

It was a subject I thought about 10 years or so back when I was thinking about systems that were basically rule-based. Back in the day my idea was that the language should eliminate many kinds of accidental complexity and should share many attributes of "low-code" systems, a particularly exotic idea I had at the time is that it is a serious weakness of mainstream programming languages that they express computations as a tree which is serial in nature and could do a bit better if they experienced computations as a graph which for one thing makes parallelism more explicit (we were working on data crunching not because we thought analytics was the prize [1] but because we needed crunched data to make the system work -- and what we found was that ordinary sprawling commercial batch jobs would wind up with early stages that either computed the same thing or shared a lot of work and could be consolidated... the computation graph let us do that optimization and take advantage of parallelism at multiple levels) Graph-based programming environments like make and Spring also free developers from having to worry about what order things have to be done in which can get really cumbersome and structurally unstable for certain systems as they get big.

I'd argue that (1) LLM systems are already trained on human language and computer language and are pretty good at the programming languages we already have and (2) the question ought to be extended to "what sorts of frameworks and libraries are easy for AI to work with?", I mean, "does an AI do better writing React or Svelte or something else?" (3) since so many programming languages and frameworks exist we can already experimentally treat "what features help AI coding" even if there is some conflation with "quality of the training data", (4) the latter might matter less than you think because, at least with human languages, LLMs seem great at transferring knowlege between languages, I mean I ask an LLM something like

    "What the hell is 无期迷途?"
and it will come back with an answer in Chinese and I'll say "I need that in English" and I get it.

Training data for a new language is not a hard problem anyway, you just have to make it! Like you could use an early draft LLM to convert large numbers of examples from other programming languages into the target language and then do some quality control on the translations like making sure tests run and stuff.

And of course the elephant in the room is what is the purpose of the system? Back in my time in the wilderness I had a lot of interest in the analytics problem because I needed it to build my database and I was mixed up in a community of analytics users and vendors but I was also interested in the "low code/no code" market for GUI applications. The requirements for these are different but the ideal solution might be "something that can access a SQL database and make a GUI for it" that lives between the worlds.

[1] ... looking back if I had to explain what the thing I was working on was it was "Something like Palantir but it runs your whole business and has 50x the TAM"

Replies PaulHoule · 2d
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.

    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.

    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 and Open in a window are one-off actions that do not change your saved default. 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.

    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. Pins, hidden stories, filters and layout are kept in this browser only.

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