A Forth-inspired language for writing websites
speckx
139 points
14 comments
May 22, 2026
Related Discussions
Found 5 related stories in 86.9ms across 8,303 title embeddings via pgvector HNSW
- The Forth Language [Byte Magazine Volume 05 Number 08] (1980) AlexeyBrin · 45 pts · March 14, 2026 · 62% similar
- Forth VM and compiler written in C++ and Scryer Prolog triska · 26 pts · March 31, 2026 · 55% similar
- Forking the Web wrxd · 120 pts · May 09, 2026 · 49% similar
- Show HN: Foundry: a Markdown-first CMS written in Go nsayoda · 22 pts · March 27, 2026 · 47% similar
- I built a programming language using Claude Code GeneralMaximus · 110 pts · March 10, 2026 · 47% similar
Discussion Highlights (4 comments)
hvs
HN Hug of Death: https://web.archive.org/web/20260522134016/https://robida.ne...
jng
LLM-based coding is enabling so much! The crazy weekend project now can have compilation to native code and web assembly, allow server-side or client-side rendering, manage multiple types of persistence, include adaptive compression, and do all of this without breaking a sweat. It's scary but I love it.
WorldMaker
> I like how weird it is. I might use it for my site, who knows? If there's a place to use a weird and fun language it is certainly one's own personal blog. Sounds like a great opportunity, I think you should do it.
Someone
> Something like this: > : h1 ( s -- ) "<h1>" emit . "</h1>" emit ; > "Hello, World!" h1 So, what’s the difference between . and emit ? It seems both take a string and output it to the HTML of the page. If so I don’t see why that couldn’t be : h1 ( s -- ) "<h1>" . . "</h1>" . ; We also have: "2026-05-21T14:00:00Z" "May 21, 2026" dt-published where, I think, the idea is to always have the two strings consistent with each other. If so, why require the blog writer to do that conversion?