• 0 Posts
  • 280 Comments
Joined 1 year ago
cake
Cake day: January 24th, 2025

help-circle


  • LoL, I mean its one of those one way connections. Like all Hollywood actors are weird theater kids but not all weird theater kids are Hollywood actors.

    And its not all, but its probably more “most”. But for the most part, some random, jock football player isn’t turning into the next big time Hollywood actor, its the kid who did an overzealous Oklahoma production.

    Actually probably not that kid either, they probably went on to broadway. Hollywood will be the one who did “a good job” as the reocuring background character.












  • I know people hate AI, but I fed the OP pic to Claude and asked it to explain the code and maybe gice modern comparisons to something like Python.


    This is AGC (Apollo Guidance Computer) assembly code from the lunar module’s landing radar routines. Let me walk through it:


    P63SPOT3 — “Is the antenna in position yet?”

    CA   BIT6
    EXTEND
    RAND CHAN33
    EXTEND
    BZF  P63SPOT4
    

    Reads a hardware channel (CHAN33) to check the state of the landing radar antenna. BZF means “Branch if Zero” — if the antenna bit is already set, skip ahead.

    if radar_channel_33 & BIT6 == 0:
        goto("P63SPOT4")
    

    “Nope, not there yet — bug the astronaut”

    CAF  CODE500
    TC   BANKCALL
    CADR GOPERF1
    

    Loads error code 500 and calls GOPERF1 — this triggers a crew alert, literally asking the astronaut to manually crank the antenna into position. The comment says it all: “PLEASE CRANK THE SILLY THING AROUND”

    display_alert(code=500, message="Antenna not in position, please fix manually")
    await_crew_response()
    

    “Did they fix it or bail?”

    TCF  GOTOPOOH  # TERMINATE
    TCF  P63SPOT3  # PROCEED — SEE IF HE'S LYING
    

    Two possible outcomes: crew hits terminate (GOTOPOOH — yes, really), or hits proceed and the code loops back to P63SPOT3 to check again. “See if he’s lying” is the actual comment, meaning: verify they actually moved it.

    if crew_pressed == "terminate":
        goto("GOTOPOOH")
    else:
        goto("P63SPOT3")  # trust but verify
    

    P63SPOT4 — “Okay, antenna’s good, initialize radar”

    TC   BANKCALL
    CADR SETPOS1
    

    Calls SETPOS1 to initialize the landing radar into position 1.

    bankcall(SETPOS1)  # configure radar for landing approach
    

    “And we’re off”

    TC   POSTJUMP
    CADR BURNBABY
    

    BURNBABY. That’s the actual name of the burn routine. Jumps to the powered descent initiation — the engine ignition sequence for landing.

    goto("BURNBABY")  # 🔥 start the descent burn
    

    The whole thing is basically: check hardware → nag human if needed → loop until fixed → initialize systems → light the engine. Written by people with a great sense of humor under enormous pressure, in 4KB of RAM.


  • I don’t get why agent based small models are not used more. Like.if the user asks.for code, load a code only model. If they want an image, load an image only model. If they want a bedtime story, load that. Etc.

    Not really supporting AI, but it feels like a way these companies could reduce costs etc, instead of these giant all or nothing models.

    Plus they could reduce pre prompting maybe? Because the coding model has no idea how to say, “make a naked celebrity image.”

    It can just fail and say “I can’t do that dave.”



  • Thats kind of his point though.

    New users, are coming from Windows. They know “the windows way”.

    Hell I had to dump all my mapped network shares on my laptop because when I wasn’t at home, the whole thing just stalls out constantly, looking for them, instead of just saying “Oh, its not there” and moving on, or just ignoring it until I actively click on it.