In today’s episode, Yud tries to predict the future of computer science.

  • corbin@awful.systemsOP
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    Indeed, this is also the case for anything packaged with #Nix; we have over 99% reproducibility and are not planning on giving that up. Also, Nix forbids network access during compilation; there will be no clandestine queries to OpenAI.

    • dr2chase@ohai.social
      cake
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      @corbin I got a 96GB laptop just so I could run (some) LLMs w/o network access, I’m sure that will be standard by 2025.🤪

      • corbin@awful.systemsOP
        link
        fedilink
        English
        arrow-up
        8
        ·
        1 year ago

        Let me know @corbin@defcon.social if you actually get LLMs to produce useful code locally. I’ve done maybe four or five experiments and they’ve all been grand disappointments. This is probably because I’m not asking questions easily answered by Stack Overflow or existing GitHub projects; LLMs can really only model the trite, not the novel.

    • self@awful.systemsM
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 year ago

      it very much fucks with me that there’s a nixpkgs working group dedicated to making NixOS an attractive platform for running LLM code. I’m guessing it comes down to two things: nix actually is very good at packaging the hundreds of specifically pinned dependencies your average garbage LLM project needs to run, and operating in the functional programming space makes these asshole grifters feel smarter (see also all the folks who contributed nothing but crypto miners to nixpkgs during that bubble)

    • dr2chase@ohai.social
      cake
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      @corbin I’m curious how they deal with the Go builder (not compiler specifically) and all its signature verification hoo-hah. There’s ways around that (and those are consistent with “trust nobody”) but it’s not usual case, and not tested nearly as hard as the default path. You can use your own builder, too, that’s also an option (and now I wonder, could we get the Go builder to export a “build plan” for other-tool consumption?)