Comments URL: https://news.ycombinator.com/item?id=47609264

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46142979

Points: 2

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=46091999

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=45978698

Points: 7

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=45604381

Points: 20

# Comments: 1

> i want to learn python and/or programming and am considering looking at the copyparty source code in that occasion

> do not

Comments URL: https://news.ycombinator.com/item?id=44537074

Points: 5

# Comments: 1

McCord began by reviewing the current scripted and templated Phoenix code generator. He then showed how a tool-invoking LLM agent could be implemented in one screen of Elixir code. The bulk of his talk demonstrated generating apps with the Phoenix.new tool. It was interesting to see the tool generate development plan and begin coding to implement the plan.

I was fascinated to hear McCord explain and critique the LLM agent as it generated a Phoenix app.

"[It's] going to come up with a plan for our app and codify that into a Markdown file."

"Now it's going to take our high-level plan and make it into an expanded plan for us and itself."

"You can say, 'I changed the plan; execute the plan.'"

"We just recursed in the server and we did a req post. It's doing a req post right now and the tokens are coming back!"

"The agent just invoked a tool, which is 'I'm going to create a file.'"

"Hopefully it does a 'surgical modify tool,' which makes it not have to modify the whole file."

"A run-time error! Oh, no! Live coding is terrible. Oh, wait. It knows I need to add some missing functions here."

"You would be like, 'Oh, no, the page broke. What happened? I'm going to look at this error.' We just send that thing back to the chat completions endpoint and magic comes out and fixes the error."

"It didn't change a web file. We should fix that."

"This is an issue that humans hit; Steff and I need to fix that."

"It added the input at the bottom. That's not ideal."

"The agent decided to idle here. ... The way I implemented this is everything the agent responds with is a tool call and it has an idle tool and that's what it invokes when it is done."

[1] https://www.youtube.com/watch?v=ojL_VHc4gLk

[2] https://phoenix.new/

In January 1979, Byte Magazine's Language Forum contained the article, "IPS, An Unorthodox High Level Language."[1] The article described IPS, a language based on Forth, but with the word names translated to German. Thus, Forth's SWAP became VERT, short for vertauschen. The intriguing article concluded with a reference to Charles Moore's 1974 paper, "FORTH, a New Way to Program a Minicomputer,"[2] which was discussed on HN in 2022.[3]

I had recently assembled a Quest Electronics Super Elf computer[4] with an expanded memory size of 4 KB. The IPS article mentioned implementations under 6 KB for 8080, 6502, and RCA COSMAC microprocessors, so I thought Forth might fit. The Super Elf included an 1861 video display controller chip, with a resolution of 64 x 128 pixels (big pixels!). I designed a font of 3 x 5 pixel characters to provide 21 lines of 16 characters. Good luck distinguishing M, N, H, U, and W without some context. I bought a (possibly surplus) keyboard from Radio Shack and screwed it onto a wedge of wood to achieve a usable typing angle.

Moore's paper described about 75 Forth words. I wrote them on index cards and jotted down Forth definitions or RCA 1802 assembly code. I wrote an 1802 assembler in Fortran to ease the conversion into 1802 machine code. I still have the printouts and punch cards in storage.

Development proceeded slowly. During a break at work, I would punch my assembly code for a few Forth words, run the assembler, and bring home the printout. That night I would load previous work into the Super Elf from cassette tape, key in the new words (and changes) via the Super Elf's hex keypad, and save back to another cassette tape. Then I would test the new Forth words and note any changes needed on the printout. Lather, rinse, and repeat until, at last, it all worked.

The finished Forth system consumed a little more than 3 KB of the 4 KB of memory. User programs, data, and Forth stacks occupied the remaining memory. The R key stuck. The @ symbol was a 3 x 5 pixel blob (this is the very important Forth memory fetch operator). But it worked!

I demonstrated the system at the local personal computer club--spun off from the local ham radio club. Based on their enthusiasm, I advanced to developing tinyForth[5] for the TRS-80, a story for another day.

[1] https://archive.org/details/BYTE-MAGAZINE-COMPLETE/197901_By...

[2] https://articles.adsabs.harvard.edu/pdf/1974A%2526AS...15..4...

[3] https://news.ycombinator.com/item?id=33134663

[4] https://www.oldcomputermuseum.com/super_elf.html

[5] https://archive.org/details/80-microcomputing-magazine-1980-...

In 1921, the steel mainmast on the six-masted schooner Edward J. Lawrence was bent as the vessel was being towed under the bridge at high tide. [2]

In 1935, the first three of four steel masts were bent as the Hamburg-American freighter Tirpitz passed northward under the bridge during an "abnormally high tide." [3]

In 1986, a radar was knocked out of commission when the South Korean freighter Hai Soo scraped the bridge while heading south. [4]

[1] https://www.nytimes.com/2025/05/17/nyregion/brooklyn-bridge-...

[2] https://www.nytimes.com/1921/02/04/archives/ship-bends-mast-...

[3] https://www.nytimes.com/1935/10/03/archives/masts-of-freight...

[4] https://www.nytimes.com/1986/04/11/nyregion/new-york-day-by-...

[1] https://forum.devtalk.com/t/how-to-run-deepseek-on-your-mac-...

Comments URL: https://news.ycombinator.com/item?id=42733109

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=42506365

Points: 1

# Comments: 0