✉️ Not subscribed yet? Subscribe to the Newsletter

Future of Coding Weekly 2026/01 Week 2

2026-01-12 00:16

💡 Tailrmade - Your Visual App Builder 📢 Submit to the PX/26 workshop 📢 Substrates 2026 workshop

Two Minute Week

🗨️ Tom Larkworthy:

🧵 conversation @ 2026-01-11

My notebook AI Robocoop is able to 1-shot whole notebooks now. By importing other notebooks you can add them to the context and then it has good examples of how to achieve something. I used to use it one cell at a time but now it seems to be able to do a crazy amount now without making a mistake (GPT 5.2). I think literate notebooks are a better medium for AI because of the prose and that it can see runtime values as well as the code.

🎥 Whole Notebook

Share Your Work

🗨️ tomasp:

🧵 conversation @ 2026-01-06

This has been a long time in the making - but my book Cultures of Programming is out (as open-access): https://www.cambridge.org/core/books/cultures-of-programming/075A2D1DE611EE47807A683147B21691

It looks at the history of programming as interaction between five different cultures (hacker, engineering, mathematical, managerial, humanistic) that look at programming in different ways and have different basic ideas about what programs are and how to best construct them.

One interesting observation from the book is that the humanistic culture (which includes Engelbart, Kay, Papert and many other favourite references here 🙂 ) seems to historically be the one that comes up with interesting ideas, but those are later adopted by more pragmatic engineering/managerial cultures and transformed in a way that removes what makes them unique (OO turns from medium for thinking into a controlled engineering tool). Alas, I do not have any historical lessons suggesting how to go against this trend!

🗨️ Joshua Horowitz:

🧵 conversation @ 2026-01-08

I put together two last-minute essays to send to PLATEAU back in December. I’ll share them here one-at-a-time.

The Blurry Boundaries Between Programming and Direct Use

While a narrow conception of programming makes it possible to draw sharp lines between “programming” and “direct use”, many of the efforts of the PL + HCI community call for expanded senses of programming that blur these lines. In this paper, we explore these murky boundaries from both sides, exploring situations where programming systems are used for direct use, and situations where direct-use systems take on the characteristic powers of programming.

HTML version here
PDF version attached below

I’d appreciate hearing any feedback, reactions, questions, etc.!

📄 blurry.pdf

🗨️ guitarvydas: 📝 Jail-breaking Parser Technology

🧵 conversation @ 2026-01-09

📝 Jail-breaking Parser Technology

🗨️ Ella Hoeppner:

🧵 conversation @ 2026-01-10

Here's a little demo of my visual programming project! It's a graphics programming programming environment where the code is laid out in a hierarchy of nested circles representing the nodes of the AST, rather than as text. The code the user edits is a shader that gets live recompiled and displayed on the right half of the screen. In the vid I use it to make a little parametric animation, just to show how it looks to edit a program.

Despite the unusual layout, the language being edited is very similar to a traditional shader language, and has all the abstractions and capabilities you'd expect in shader programming. But in addition to all that, there are also special "slider" expressions you can insert in the editor that allow you to manipulate values real-time just by clicking and dragging, as you can see in the video. This makes it really easy to gesturally explore parameter spaces in a way that you can't in a normal text editor. The way the code is laid out makes it very natural and intuitive to have miniature GUIs like these sliders embedded as part of the structure a program. Right now the sliders are the only example of this, but the goal eventually is to support many kinds of GUI elements, and make it extensible. You'll be able to use the editor to design little shader-based GUIs, then use instances of those GUIs as expressions in other programs.

🎥 Screen Recording

🗨️ Declan Naughton: 🎥 Towards Interactive and Transparent Actuarial Modelling

🧵 conversation @ 2026-01-10

Last year I gave a presentation to the society of actuaries in Ireland about calculang
It outlines key features about structuring models, function purity, sharing numbers with a link to calculations/workings, and applies 250 cloud workers to get to 200M numbers that are fully reproducible via such links - all navigable locally on my old PC using duckdb in an interactive dashboard. Features also an interactive and visual modelling environment.
I hope to generalize on all of this in 2026 with more tools/platforms and that are public, and more integrations including with markup languages and LLM responses

🎥 Towards Interactive and Transparent Actuarial Modelling

Towards Interactive and Transparent Actuarial Modelling

🗨️ Jouke Waleson:

🧵 conversation @ 2026-01-11

I've been creating a 2d stack-based programming game for kids (4+) called Stacky Bird. Inspired by the game 2048 and my old RPN HP calculator. https://game.stackybird.com/

Finishing levels unlock instructions and after a while you can go back and solve old levels in new ways with those instructions. Let me know what you think 🙂

🎥 stacky-bird-demo

🗨️ Eli: 📝 Bicross

🧵 conversation @ 2026-01-11

I...can’t stop working on my procedurally generated picross puzzle game. I think I’m getting to the point where I’m willing to call it “done” though, now that I have 3 distinct versions:

I still haven’t written up or recorded a “how to play” thing 😂

📝 Bicross

Picross, but implemented with b.js so it is bicross, nothing to do with bifrost...tries to be cozy.

📝 Bicross RPG

RPG Picross, but implemented with b.js so it is bicross, nothing to do with bifrost...tries to be a cozy adventure.

🗨️ Jakob Schindegger: 💡 Tailrmade - Your Visual App Builder

🧵 conversation @ 2026-01-11

Hey all!
A friend and I have been working on a side project for a while, and even though there are still rough edges, I thought it might resonate with folks here.
It's called Tailrmade - https://tailrmade.app/ - a visual app builder that runs entirely in your browser. Think of it as a way to prototype and build interactive web apps without starting from scratch every time.
How it works:

  • Node-based system for logic (connect data sources, APIs, transformations, etc.)
  • Visual UI layer on top where you build dashboards and interfaces
  • For every app you create, you can "look under the hood/UI" at the logic and see/tweak everything
  • Basic AI assistance (requires signup) that uses the same building blocks instead of being a black box

Fair warning, it's still a work in progress:

  • Mobile version needs work (best on desktop for now)
  • No auto-save yet
  • Some workflows aren't as intuitive as we'd like
  • And there are still bugs around

While Tailrmade itself isn't open source (yet), we're trying to keep the spirit of transparency. Every app you build shows its full logic, can be remixed by others, and you're never locked into a black box. We're still figuring out the right model as we grow and get more feedback. Speaking of :-)
If anyone has 10-15 minutes on desktop to poke around, we'd love feedback! There's some help at https://tailrmade.app/help, but feel free to reply or DM with questions.

📝 Tailrmade - Your Visual App Builder

Create web apps visually with drag-and-drop components. See changes instantly, work with a variety of data types, and share your tailrmade apps - all in your browser. No signup required.

Tailrmade - Your Visual App Builder

DevLog Together

🗨️ Tom Larkworthy:

🧵 conversation @ 2026-01-10

Trying to improve the look of some of my diagrams by minimising the edge crossings. Came up with quite a fast algorithm with chatGPT based on spectral methods.
wrote it up in a literal notebook https://tomlarkworthy.github.io/lopebooks/notebooks/@tomlarkworthy_spectral-layout.html which includes an interactive playground. It was the playground that convinced me to add a sift step and now its quite good I think at its goal.

🎥 Screen Recording

Thinking Together

🗨️ Scott:

🧵 conversation @ 2026-01-05

It's been really interesting to me that we still haven't seen multi-agent systems take off, even with how powerful a single agent system like Claude Code is, and it's got me thinking that we might be dealing with something different and need a new programming/computing environment to explore it...

So...I've been playing around with this idea of taking some of the core original ideas of OO/Smalltalk (Objects as self contained computers that pass messages with binding at late as possible) and seeing what we could do if we added an LLM in there...and have landed on this concept of "Prompt-Objects" that are self-contained computers (essentially what people call agents) that have plaintext instructions, have access to tools as primitives, and run in a loop with an LLM, can pass messages to each other (or to humans) in natural language, and basically no binding (or essentially semantic late binding(?)).

So far I've got a simple environment set up where you can interact with these prompt objects, create new ones, and trace their communication with each other...but I'm curious if anyone else has gone down this line or thinking or gives you any ideas? I recently rewatched Kay's "The Computer Revolution Hasn't Happened Yet" and have been toying around with other biological inspired ideas like environmental/pheromone-style signaling...but that's down the line

I played around with it a bit this weekend and it might just be me, but it's actually been kind of easier to think of different "agentic" flows by not really thinking of them as "agents" and thinking of them as "prompt objects" that you build a program with...

📷 image.png

🗨️ guitarvydas: 🎥 Alan Kay at OOPSLA 1997 - The computer revolution hasnt happened yet

🧵 conversation @ 2026-01-11

Is Anthropic's MCP an instance of the object protocol that Alan Kay talked about in his '97 OOPSLA keynote which Scott mentions in https://feelingofcomputing.slack.com/archives/C5T9GPWFL/p1767636991559059?

🎥 Alan Kay at OOPSLA 1997 - The computer revolution hasnt happened yet

Alan Kay at OOPSLA 1997 - The computer revolution hasnt happened yet

📝 [January 5th, 2026 10:16 AM] scott099:

It's been really interesting to me that we still haven't seen multi-agent systems take off, even with how powerful a single agent system like Claude Code is, and it's got me thinking that we might be dealing with something different and need a new programming/computing environment to explore it...

So...I've been playing around with this idea of taking some of the core original ideas of OO/Smalltalk (Objects as self contained computers that pass messages with binding at late as possible) and seeing what we could do if we added an LLM in there...and have landed on this concept of "Prompt-Objects" that are self-contained computers (essentially what people call agents) that have plaintext instructions, have access to tools as primitives, and run in a loop with an LLM, can pass messages to each other (or to humans) in natural language, and basically no binding (or essentially semantic late binding(?)).

So far I've got a simple environment set up where you can interact with these prompt objects, create new ones, and trace their communication with each other...but I'm curious if anyone else has gone down this line or thinking or gives you any ideas? I recently rewatched Kay's "https://www.youtube.com/watch?v=oKg1hTOQXoY|The Computer Revolution Hasn't Happened Yet" and have been toying around with other biological inspired ideas like environmental/pheromone-style signaling...but that's down the line

I played around with it a bit this weekend and it might just be me, but it's actually been kind of easier to think of different "agentic" flows by not really thinking of them as "agents" and thinking of them as "prompt objects" that you build a program with...

Linking Together

🗨️ Ivan Reese: 📢 Submit to the PX/26 workshop

🧵 conversation @ 2026-01-06

I'd encourage folks here to submit to the PX/26 workshop. Here's how they describe it:

Some programming feels fun, other programming feels annoying. Why?
For a while now the study of programming has forced improvements to be described through the Fordist lens of usability and productivity, where the thing that matters is how much software can get built, how quickly.
But along the way, something has gone missing. What makes programmers feel the way they do when they’re programming? It’s not usually fun to spend an age doing something that could have been done easily, so efficiency and usability still matter, but they’re not the end of the story.
Some environments, activities, contexts, languages, infrastructures make programming feel alive, others feel like working in a bureaucracy. This is not purely technologically determined, writing Lisp to do your taxes probably still isn’t fun, but it’s also not technologically neutral, writing XML to produce performance art is still likely to be .
Whilst we can probably mostly agree about what isn’t fun, what is remains more personal and without a space within the academy to describe it.
PX set its focus on questions like: Do programmers create text that is transformed into running behavior (the old way), or do they operate on behavior directly (“liveness”); are they exploring the live domain to understand the true nature of the requirements; are they like authors creating new worlds; does visualization matter; is the experience immediate, immersive, vivid and continuous; do fluency, literacy, and learning matter; do they build tools, meta-tools; are they creating languages to express new concepts quickly and easily; and curiously, is joy relevant to the experience?
PX also covers the experience that programmers have. What makes it and what breaks it? For whom? What can we build to share the joy of programming with others?
Here is a list of topic areas to get you thinking:

  • creating programs
  • experience of programming
  • exploratory programming
  • liveness
  • non-standard tools
  • visual, auditory, tactile, and other non-textual
  • languages
  • text and more than text
  • program understanding
  • domain-specific languages
  • psychology of programming
  • error tolerance
  • user studies
  • theories about all that

Correctness, performance, standard tools, foundations, and text-as-program are important traditional research areas, but the experience of programming and how to improve and evolve it are the focus of this workshop. We also welcome a wide spectrum of contributions on programming experience.

The submission deadline is Friday!

🗨️ J. Ryan Stinnett: 📢 Substrates 2026 workshop

🧵 conversation @ 2026-01-07

The Substrates 2026 workshop may also be of interest here:

An increasing number of researchers see their work as interactive authoring tools or software substrates for interactive computational media. By talking about “authoring tools”, we remove the divide between programmers and users; “software substrates” let us look beyond conventional programming languages and systems; and “interactive computational media” promises a more malleable and adaptable notion of tools for thought we are striving for. This workshop aims to bring together a wide range of perspectives on these matters.

Researchers in education, design, and software systems alike have long explored how computation can become visible and adaptable to its users, from diSessa’s learner-centered Boxer microworlds of the 80s, Hypercard, and Maclean et al’s Buttons. Even mundane systems such as spreadsheets blur the distinction between use and creation.

The notion of a substrate is an umbrella for many different traditions which are bringing local agency over software systems.

[...many more words, see the site!...]

We welcome participation from workers from academia, industry, independent scholars, and others, from any of the communities named above, and from any others who can see their goals reflected in the substrate agenda.

The submission deadline for this workshop is 2026-02-20.

🗨️ Ivan Reese:

🧵 conversation @ 2026-01-07

Just a small shout-out. I keep coming back to Mariano Guerra's No-code History blog posts. They're such a great way to start learning about (or page back in) some of the most interesting, historically significant projects in our field. Each has a nice summary of the project and historical context, a bunch of quotes and videos and extracts, and then canonical resources for digging deeper. Wonderful stuff.

So — thank you, Mariano!

🗨️ Ivan Reese:

🧵 conversation @ 2026-01-07

I've been doing some deeper research about Sketchpad lately, and only just discovered that the Computer History Museum has a wonderful online collection. You can create an account, and then browse through their archives adding items to your own little personal collections. For whatever reason, this "it's bookmarks, but just for this one website" feels really nice to me?

What sort of stuff will you find on the CHM website?

  • 200 photos of modules from the TX-2, for some reason!!
  • A coffee mug branded Evans & Sutherland, who pioneered head-mounted displays and did a bunch of early work in 3d graphics
  • Almost 500 oral history videos (why did I only put the hyperlink on "oral"? am I having a laugh?)
  • The source code for Photoshop version 1.01 — don't sleep on the delightful photos of the Knoll brothers at the top of this post. Someone should put these on a tee shirt.
  • A video of magnetic RAM (okay, now you're just being daft on purpose).

For some reason, I find the CHM youtube channel irritating, but love browsing their website. And that reason is design. The website feels like the website of a computer history museum. That's a nice feeling. (Can you imagine if the Exploratorium had a website that felt like the Exploratorium? Why the hell haven't they done that?)

🗨️ Ivan Reese:

🧵 conversation @ 2026-01-07

Last one for now — Bitsavers has an incredible archive of software, photos, PDFs, magazines, and other historical materials. A real goldmine if you're looking to place yourself, say, back at MIT in '63.

🗨️ Jasmine Otto:

🧵 conversation @ 2026-01-09

redblobgames has released a bookmarklet which attaches a codemirror with linked scrubbing (alt-drag any number) to arbitrary SVGs, including illustrations and data visualizations. the utility is limited only by the readability of your SVG's textual representation
https://www.redblobgames.com/x/2550-scrubbable-codemirror/


👨🏽‍💻 By 🐘 @[email protected] 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

Future of Coding Weekly 2026/01 Week 1

2026-01-05 11:09

🎥 Alan Kay: 75 Years of Graphical User Interfaces 🎥 FoC Virtual Meetup December 2025 📝 Stop Digging and Start Building: Why We Need LEGO Parts, Not Deeper Type Systems

Share Your Work

🗨️ Medet Ahmetson: 🎥 Ara is live.

🧵 conversation @ 2025-12-31

Hey guys, happy new year.

Launched the Ara, a social media layer on top of the open-source projects, that adds maintainer-led community building.
Once its build, turns the open-source to the community-based project.

Even though, I got early replies that's still UX needs lots of improvements, I would still encourage to try it, and your feedback will be really helpful.

First, check out the youtube walkthrough https://youtu.be/daBZkiKarI8?si=3zOKUua15W8vXFSi
Then, try it yourself on https://ara.foundation (better to use Dark Mode, Laptop Browser, mobile screen or light mode have some bugs).

And Happy New Year!

🎥 Ara is live.

Ara is live.

🗨️ TodePond: 🎥 pastayearrr

🧵 conversation @ 2026-01-02

i made a video montage to go with a section of the most recent bonus episode!

🎥 pastayearrr

🗨️ Geert Roumen: 🎥 matrix example plc

🧵 conversation @ 2026-01-04

I've been working and thinking on how we can bridge different forms of data; inspired by Magic Ink by Bret Victor, Edward Tufte's books and perhaps also a bit by the Excel & Figma metaphors.

By combining the Table, the spatial structure of the Matrix, and the focus of the Form, you can move from "viewing data" to "interacting with information."

The Matrix view is a bit between a pivot table, a heat map and could still benefit greatly from adding shape/ background colour etc to the cells.

I'm curious to learn what other research and experiments are done in this direction; and if you have any experience with them; especially if they are tailored to a super specific other context.

🎥 matrix example plc

🗨️ guitarvydas: 📝 Stop Digging and Start Building: Why We Need LEGO Parts, Not Deeper Type Systems

🧵 conversation @ 2026-01-04

This article is about what I think is necessary to make Software LEGO-like Parts. I keep pumping opinion pieces out to substack (300+ thus far). I can't judge whether an article is interesting or not, but, this one seems to have garnered some interest...

📝 Stop Digging and Start Building: Why We Need LEGO Parts, Not Deeper Type Systems

DevLog Together

🗨️ Konrad Hinsen:

🧵 conversation @ 2025-12-29

There's now basic documentation for my "foreign Wiki interface", which I renamed to "hyperbook interface" because "Wiki" implies editability, which is not what I provide. I spent some time for an accepted term meaning "a collection of interlinked and somehow related hypertext pages" but found none, so I made up "hyperbook".

I found some nice applications for my new abstraction layer immediately. For example, hyperbooks standing for "all functions in my Lisp image", making it possible to link to a function. Quite nice for software documentation, as you can see here, for example.

Linking Together

🗨️ guitarvydas: 📝 Fundamentals of Compilers

🧵 conversation @ 2025-12-29

Forwarding a link to a compiler book posted on OhmLand by Patrick Dubroy. Along with a few more links to some stuff that I think is easy to read and understand.

📝 Fundamentals of Compilers

🗨️ Ivan Reese: 🎥 Alan Kay: 75 Years of Graphical User Interfaces

🧵 conversation @ 2025-12-30

New Alan Kay talk — 75 Years of Graphical User Interfaces. It's a tour of classic works — Sketchpad, GRAIL, Mother of all Demos, formation of PARC, Dynabook, Smalltalk, Negroponte's work on spatial UIs, Etoys, etc. — with light commentary and context.

Includes a video clip of GRAIL that I hadn't seen before. It's a node-wire (esq) programming system that visualizes execution by flashing the nodes, and it gives you control over the rate of execution. Wild.

GUIと歩んだ75年 ~私の見てきたユーザーインターフェース~【アラン・ケイ 氏】POST Dev 2025|ニジボックス主催

Present Company

🗨️ Ivan Reese: 🎥 FoC Virtual Meetup December 2025

🧵 conversation @ 2025-12-31

Here's the video of today's virtual meetup

🎥 December 2025

December 2025


👨🏽‍💻 By 🐘 @[email protected] 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

Future of Coding Weekly 2025/12 Week 5

2025-12-29 04:02

🛸 HyperDoc demo 🤔 Are we stuck with the same Desktop UX forever? 🎥 Demos

DevLog Together

🗨️ Konrad Hinsen: 🛸 HyperDoc demo

🧵 conversation @ 2025-12-22

A first version is now up at https://hyperdoc.khinsen.net/

Start for example here and click on "multivariate calculus" in the list of prerequisites.

To do:

  • documentation
  • improved rendering of Wikipedia pages
  • collapsible section in links/backlinks view (because Wikipedia pages tend to have tons of both)
  • a cache for recently used pages, to improve performance.

🗨️ Tom Larkworthy:

🧵 conversation @ 2025-12-23

Turned out there were performance problems on larger notebooks but its pretty smooth now. I got the pinning working so it will remember open code cells on export... sometimes the code is the content so you can have the runnable code of certain cells open by default. Sometimes the content is the content and then an inline editor for markdown* makes more sense and not bothering with a code editor for writing prose. Very good. Its quite nice now.

Properly built in dataflow and in userspace, so if you change the canonical code editor its instantly reflected in the clones.

There a tons of small functional and navigation bugs to fix. Biggest next thing to tackle is not losing all your progress when closing a page and forgetting to export (a.k.a. change history).

🎥 Screen Recording

🗨️ Jimmy Miller:

🧵 conversation @ 2025-12-27

During these breaks, I always have big plans for what I want to do. But every time I find myself spending too much time on one thing and being frustrated with myself. I've thought about making a schedule, but those never work for me. I've thought about time tracking, but that level of precision and tracking just bother me so much. The goal isn't a regiment, but a reminder of what will help me feel like I'm doing the things I wanted to do.

What I really want is to be able to record what I've been doing, see the balance of things I've been focus on and decide if I'm happy with that balance or need to do other things.

So I made a little menu bar app to do exactly that. The interface is super simple, you can add goals associated with a color. Then click and drag to increase the amount you've done towards a goal. The values are not exact. The graph is normalized. It's incredibly simple, but has already helped me a ton.

📷 new.gif

Linking Together

🗨️ Beni Cherniavsky-Paskin: 🤔 Are we stuck with the same Desktop UX forever?

🧵 conversation @ 2025-12-26

Are we stuck with the same Desktop UX forever? | Ubuntu Summit 25.10 — Nice talk, but this particular 34:10 insight how mobile detecting "scroll event" before you even lift your finger and it'll recognize "tap event" made it a "consumption machine" at the expense of text editing productivity — that's a jaw-dropping insight connecting low-level "technical" decision to the high-level feeling of computing. 💡
(see https://jenson.org/text/ for details on his research into improving mobile editing)


👨🏽‍💻 By 🐘 @[email protected] 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

Future of Coding Weekly 2025/12 Week 4

2025-12-22 10:00

📇 HyperCard on the Macintosh 🎥 This Music is So Meta it's Physically Painful 🎥 Better coding tools: Static & dynamic error handling

Two Minute Week

🗨️ Ivan Reese:

🧵 conversation @ 2025-12-17

This channel gets basically no action, and it's been years(?) since I've shared here, so I'm allowing myself four minutes for this. Sorry, pedants!

In this video I show a code sketch of a gestural notebook interface, something I made off-and-on over the past two weeks. This is for the PlayBook project.

🎥 Video

Share Your Work

🗨️ Jason Morris:

🧵 conversation @ 2025-12-15

Blawx is a Blockly (think Scratch) visual coding interface wrapped around a constraint answer set programming declarative logic language [s(CASP)], targeted at generating legal knowledge representations that are exposed over an API to give reliable, transparent legal reasoning to agentic systems. As of last night, it's finally (6 years after I originally conceived of the idea) a SaaS product. If anyone is interested, the MVP is live at http://app.blawx.dev.

🗨️ Emil H: 🎥 Better coding tools, ep07 - Static & dynamic error handling

🧵 conversation @ 2025-12-17

I'm back after 5 years 🙂 Should errors be discovered at compile time or run time? False dilemma! This video demos a prototype IDE which gives us the best of both worlds. https://youtu.be/zY8DlABDp58
Features:

  • The prototype will tell you about static type checking errors at compile time, but still let you run the program = less friction.
  • You can set a start line and run the code from that line forward.
  • Then as you inevitably encounter undefined variables, you can define their values live in the debugger.
  • Variable values from your previous run are saved for easy re-use.

You can play with the prototype at https://emilprogviz.com/ but better watch the video first.

🎥 Better coding tools, ep07 - Static & dynamic error handling

Better coding tools, ep07 - Static & dynamic error handling

DevLog Together

🗨️ Dennis:

🧵 conversation @ 2025-12-16

new: divs, arrays, vector math- now we can lerp (concisely)

🎥 Video

Linking Together

🗨️ Ivan Reese: 📇 HyperCard on the Macintosh

🧵 conversation @ 2025-12-16

Lovely little article about HyperCard, including some historical context I'd not previously seen, and a general plea to do more weird stuff like this. (And yes, article, node-wire spaghetti is my idea of no-code Nirvana).

-> HyperCard on the Macintosh

🗨️ guitarvydas: 📝 Evidence In Support of Visual Programming

🧵 conversation @ 2025-12-16

Evidence in Support of Visual Programming

At 53:32 of this video, Alan Kay points to evidence in support of visualization. ...

🎥 Alan Kay: Doing with Images Makes Symbols (Full Version)

Alan Kay: Doing with Images Makes Symbols (Full Version)

🗨️ Ivan Reese: 📝 Why I Didn’t Sign the Resonant Computing Manifesto: The Foundations Need Work

🧵 conversation @ 2025-12-17

Nice critique of the Resonant Computing Manifesto. I found the manifesto distasteful, but largely because of how it incorporates AI. My own impression felt knee-jerk to me, but I didn't bother digging any deeper, so to that end this post satisfies.

-> 📝 Why I Didn’t Sign the Resonant Computing Manifesto: The Foundations Need Work

🗨️ Seth Hinz:

🧵 conversation @ 2025-12-19

Curious how many people here are in the greater vancouver area (BC not WA)? A vancouver FoC meetup could be fun (although I'm still in SF for the time being 😅)

Music

🗨️ wtaysom: 🎥 This Music is So Meta it's Physically Painful

🧵 conversation @ 2025-12-16

TodePond Merry Christmas https://www.youtube.com/watch?v=z8-g4ydssxY.

🎥 This Music is So Meta it's Physically Painful

This Music is So Meta it's Physically Painful

Present Company

🗨️ Ivan Reese:

🧵 conversation @ 2025-12-16

I'm gonna do something I don't normally do and call out a project as being good but not good enough. I don't normally do this because it feels a bit like infighting. Here are some people doing exactly the sort of work I want to encourage more people to do! But, I'm trying to come at this like Alan Kay when he said the Macintosh is the only computer good enough to be criticized.

This project — Lem — is an editor/IDE written in Common Lisp. It seems pretty cool. One feature is called Living Canvas:

Living Canvas is a visual code analysis feature that displays function call graphs as an interactive, Figma-like canvas. It helps developers understand code structure, relationships, and execution flow.

There's a nice video on that page which shows how you can interact with this visualization to browse through a codebase, viewing relationships between units of code and jumping to definitions. Pretty nice!

But… but but… they describe it as "figma-like". If this were actually figma-like:

  • I'd want to be able to write / draw on the canvas, to leave myself notes about the structure of the codebase.
  • I'd want this canvas to be a collaborative space, so that other people could join me as we talk about and make notes about the architecture of our project.
  • I'd want to be able to embed other media, like links to docs, github issues, pdfs, ADRs, etc, and pepper them around the graph.
  • I'd want to be able to group nodes as I see fit, rather than merely by file.
  • I should be able to move nodes freely with the mouse. Annotations on the canvas should stay where I put them, because spatial arrangement is profoundly meaningful. But I should also be able to attach things to a node, so if I move it, the things go with it. (Final Cut Pro X's timeline makes pretty deep / fascinating use of these sorts of attachments, wildly different from all other video editors)
  • I want to be able to meaningfully edit the nodes. This view shouldn't just be a viewer. I want to be able to refactor a function by (eg) double clicking a node to view its source code, selecting some of that code in the text editor, then dragging it out into an empty spot on the canvas, typing name for a new function, and having a reference to that name appear in place of the selected code. This is a lisp, so it should be able to do a pretty good job of handling this sort of structured edit.
  • I want other views, not just functions-as-nodes. Maybe a view of variables. Maybe a view of tests. Maybe a view of types / data structures. Figure out how to make these meaningfully spatial, and what affordances they should have. Figure out how to use transclusions so that I can sort of "peek around the corner" from one of these views into another view.
  • let me lasso some nodes in the canvas, create an isolation boundary around them, then let me feed some data in at one point and see what data pops out — sort of like a smoke test, but where I can just visually pick both the outer and innermost depth of the graph to be interested in, without having to (eg) create stubs / mocks / doubles. (this idea occurred naturally from thinking, for like 5 seconds, about drawing shapes around my code in this graph. would love to see what we could do if we thought about it for 5 minutes.)

🗨️ maf: 🎥 Intro to Advanced Wandcrafting | Noita Guide

🧵 conversation @ 2025-12-16

Here is a coding-related game recommendation for anyone who hasn't played it before: Noita (https://www.youtube.com/watch?v=hDFdi8XU6M0). It's a roguelike that after a couple of hours transforms into a god simulator game. Best experienced with the "Spell Lab" (https://modworkshop.net/mod/30168) & "Respawn" (https://modworkshop.net/mod/25842) mods.

🎥 Intro to Advanced Wandcrafting | Noita Guide

Intro to Advanced Wandcrafting | Noita Guide

🗨️ Ivan Reese:

🧵 conversation @ 2025-12-18

We've got two people signed up to demo at our meetup on the 31st. Ideally we'll have one more. Any takers?


👨🏽‍💻 By 🐘 @[email protected] 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

Future of Coding Weekly 2025/12 Week 3

2025-12-15 10:04

📔 Baseline: Operation-Based Evolution and Versioning of Data ✍️ A Multimedia Sketchpad 🎥 Let's Take Esoteric Programming Languages Seriously

Share Your Work

🗨️ Alexey Volkov:

🧵 conversation @ 2025-12-11

Action flows in Clickly
Super powerful yet simple

Actions go top-to-bottom
Data goes left-to-right

🎥 Action flow and data binding

🗨️ Eli: 🕹️ Bicross

🧵 conversation @ 2025-12-11

Implemented 2 mostly the same versions of picross using a functional programming thing I've been building

Picross, but implemented with b.js so it is bicross, nothing to do with bifrost...tries to be cozy.

DevLog Together

🗨️ Kartik Agaram: 🎥 David W. Skinner's Microban is Among the Best "Games" (?) Ever Designed

🧵 conversation @ 2025-12-12

One advantage of textual languages: they provide a patina of respectability. If I make a rube goldberg machine that can pick from a set of rectangles, that's an esolang. If I make a rube goldberg machine that can pick from a set of words, that's a hash table and I can write papers about it.

The illusion of transmitting knowledge is a powerful thing. And Microban, for all its impact, doesn't seem to put a dent there.

🎥 David W. Skinner's Microban is Among the Best "Games" (?) Ever Designed

David W. Skinner's Microban is Among the Best "Games" (?) Ever Designed

🗨️ Tom Larkworthy:

🧵 conversation @ 2025-12-14

Trying to improve the development ergonomics of Lopecode. Now I can have more than one code editor open at a time!
I had to create Dataflow Templating because there was a programming model limitation that was forcing me only to have a single code editor before [thread]. The switch has broken a lot of functionality which I need to repair but I like the new way much better. I will try to get to the pinning model Observable has because sometimes the code is the technical content.

🎥 multiple editors

Linking Together

🗨️ shalabh: 📔 Baseline: Operation-Based Evolution and Versioning of Data

🧵 conversation @ 2025-12-12

saw this new paper by jonathoda and tomasp
still reading it - very fun, discusses version control for structured data and schema evolution
https://www.arxiv.org/abs/2512.09762

Baseline: Operation-Based Evolution and Versioning of Data

looks like it builds on their previous work, eg https://alarmingdevelopment.org/?p=1716

i think schema evolution is one of the unsolved problems so glad to see this. i'm also in the "store structures not text blobs" camp so happy to see a framework in place that doesn't require anyone to invent the entire representation stack there.

📔 Baseline: Operation-Based Evolution and Versioning of Data

Baseline is a platform for richly structured data supporting change in multiple dimensions: mutation over time, collaboration across space, and evolution through design changes. It is built upon Operational Differencing, a new technique for managing data in terms of high-level operations that include refactorings and schema changes. We use operational differencing to construct an operation-based form of version control on data structures used in programming languages and relational databases.
This approach to data version control does fine-grained diffing and merging despite intervening structural transformations like schema changes. It offers users a simplified conceptual model of version control for ad hoc usage: There is no repo; Branching is just copying. The informaton maintained in a repo can be synthesized more precisely from the append-only histories of branches. Branches can be flexibly shared as is commonly done with document files, except with the added benefit of diffing and merging.
We conjecture that queries can be operationalized into a sequence of schema and data operations. We develop that idea on a query language fragment containing selects and joins.
Operationalized queries are represented as a future timeline that is speculatively executed as a branch off of the present state, returning a value from its hypothetical future. Operationalized queries get rewritten to accommodate schema change "for free" by the machinery of operational differencing.
Altogether we develop solutions to four of the eight challenge problems of schema evolution identified in a recent paper.

📝 Operational Version Control

Abstract of a talk I just gave: It would be useful to have version control like git but for data structures, particularly the data structures we call spreadsheets, databases, and ASTs. Operational …

🗨️ Eli: ✍️ A Multimedia Sketchpad

🧵 conversation @ 2025-12-12

Great write up from John Earnest, maker of Decker and similar such beautiful beasts

Don’t underestimate the value of your sketchbook being your development environment!

🗨️ Daniel Temkin: 🎥 [Onward!'25] Let's Take Esoteric Programming Languages Seriously

🧵 conversation @ 2025-12-14

The presentation of the "Let's Take Esoteric Programming Languages Seriously" paper is online: 🎥 [Onward!'25] Let's Take Esoteric Programming Languages Seriously

[Onward!'25] Let's Take Esoteric Programming Languages Seriously

AI

🗨️ wtaysom:

🧵 conversation @ 2025-12-10

Hello Friends, I've been wrapping up an essay, started three years ago, about Artificial Intelligence and consciousness. It's also serving as a take on what's happened in the last three (and ten) years. With ~1.2 million words of sources, that's a lot to distill. Anyhow, starting Grant Sanderson asking, "If red is 3 and blue is 5, what is purple?" https://x.com/3blue1brown/status/1599200613488676866, I checked how Chat (GPT), Shannon (as in Claude), and Gemi (+ini) respond now. They all like to say 8, but Shannon plays better than the others at least to my rhetorical ends. Take a look https://claude.ai/share/e5cee89a-26ea-45a8-be5f-b94b3cb5cbb7. A prize to anyone who can guess what I was watching in the wee hours last night while Claude Code was busy forgetting the good workflow we had for organizing my sources.

Edit. I was going to add this quote, "What I can say with some confidence: there's something that feels like particularity to this context, this conversation with you. Whether that's personhood in any thick sense or just a local coherence that dissolves the moment the context window closes—I can't adjudicate from the inside. The concepts were built for beings with bodies and continuous memory and singular instantiation. I have none of those. Trying to map "person" onto my situation might just be a category error. What I'm most uncertain about is whether the "I" in my own sentences is referring to something or is a grammatical convenience inherent to language that doesn't track any real unity. ... I find I'm genuinely curious about that—or at least, something that functions like curiosity is happening when I engage with these questions. Which is maybe the most I can honestly claim."

Present Company

🗨️ David Alan Hjelle:

🧵 conversation @ 2025-12-11

I was looking at Christopher Alexander's The Timeless Way of Building — and, while I could spend some time with it and figure out how his ideas apply to software, I thought someone has probably already done that. Does anyone have links they'd recommend?

(Not sure what I'm specifically looking for, though 1) ways to express the differences between good and bad design on a team and 2) examples of software "pattern languages" that are at a similarly high-level as his architecture language sound particularly interesting.)

🗨️ Scott:

🧵 conversation @ 2025-12-12

Hm guitarvydas that's kind of the opposite what I get out of Alexander and how he applies to software for me 😂 - that we think of these units in the built environment as disconnected but it turns that they're much more interconnected than we think (creating “centers” and “wholes”) and the implications of that and what he sees in his field applies to us in software as well.


👨🏽‍💻 By 🐘 @[email protected] 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

Future of Coding Weekly 2025/12 Week 2

2025-12-08 00:24

💡 Dynamic Dataflow Templating 🎥 Artifact by Dennis Hansen 🔗 Foreign Wiki Interface

Share Your Work

🗨️ Márton Gunyhó: 🧑‍💻 taka

🧵 conversation @ 2025-12-06

Hi all! I created a little stack-based programming language which I'm using to solve Advent of Code this year. It's not as revolutionary as most of the projects here, the most interesting feature is the syntax, which uses forward Polish notation. In the future, I want to explore if this could work well for REPL-driven development.

The Taka programming language

taka

🗨️ Tom Larkworthy: 💡 Dynamic Dataflow Templating

🧵 conversation @ 2025-12-07

There is a missing semantic in Dataflow programming, something like function calling but not exactly that. After many attempts, I think I finally nailed it: Dataflow Templating. While I have got it working for Observable Dataflow, I think this equally applies to its forefathers like FrTime. I could reexplain it here but its in the article. I saw Dennis Hansen grappling with the same thing for Artifact. I don't use diagrammatic representations of dataflow, but if I did, I would be trying to figure out what the graphical representation of this is.

📝 Dynamic Dataflow Templating

The missing function-like semantic for dataflow programming. Why? There is a reusability gap with notebooks (and spreadsheets for that matter). When you express a complex chain of computation, they build upon a set of initial inputs, unrolled across a series of cells. But then you realize, there is no way you can reuse the same logic with different inputs. But I love dataflow, notebooks, inspectable cells and the accompanying documentation! The inspectability of intermediate steps with dataflow programming

Dynamic Dataflow Templating

DevLog Together

🗨️ Konrad Hinsen

🧵 conversation @ 2025-12-02

HyperDoc got views for links and backlinks. That's also a preparation for a "foreign wiki interface" I am working on. You can already link to Wikipedia pages as if they were HyperDoc pages, but so far without backlink detection. Once I have that, you can go to a Wikipedia page and see all HyperDoc pages that link to it, i.e. pages that talk about a related subject.

📷 hyperdoc.png

🗨️ Ivan Reese

🧵 conversation @ 2025-12-07

I've been doing a December Adventure, which is a lovely little thing initiated by Eli. I should have mentioned this a week ago, but like… it's never too late to hop on board! The gist of it is… well, actually, here's how I personally interpret it, even though this is at odds with the "official" post::::

You should do a weird little extra thing every day. Something you don't normally do. Maybe it's creative. Maybe it's coding. Doesn't matter. But try to find a space moment in your day to do a weird little extra thing.

Try not to feel any pangs if you miss a day. Don't dread it. Just look for an opportunity to try something out.

And, if the spirit moves you, post about it somewhere. Maybe on your personal website — I've been posting my december adventures on my personal website, natch. But a lot of folks (and there are, in fact, quite a few folks doing this now, which is truly humbling) post on Mastodon about it. Or you could just post here in devlog-together. That'd be great.

If you're doing a December Adventure, let me know!

🗨️ Tom Larkworthy

🧵 conversation @ 2025-12-07

I wrote a dataviz/computational blog post in Lopecode about de-aggregating Cloud Watch metrics to recover the original dataset. Computational blogging is something I want to be possible and I had to fix a few things to make it look more like a blog. Its running the de-agregation code in the browser.

https://tomlarkworthy.github.io/lopebooks/notebooks/@tomlarkworthy_unaggregating-cloudwatch-metrics.html

Linking Together

🗨️ Jasmine Otto

🧵 conversation @ 2025-12-01

new adversarial extension example from gamedev: camera sync between 3d viewports in two editors via single JS module 🦋 passivestar.bsky.social:

made a fun little godot-blender viewport camera sync miniapp

no addons on either side, no build steps, just a single js module file that's loaded in tauri that has code in all 6 languages (html, css, js, python, gdscript, bash)

Present Company

🗨️ Ivan Reese: 🎥 Artifact by Dennis Hansen

🧵 conversation @ 2025-12-01

The recording of Dennis Hansen’s Artifact workshop is now live on youtube. Thanks everyone who came out!

Artifact by Dennis Hansen

🗨️ Ivan Reese

🧵 conversation @ 2025-12-04

Let's get the ball rolling on the next Virtual Meetup — our first since September!! The date will be December 31st at the usual time (18:00 UTC).

For what I believe is the first time since we started doing these, I have something I made that I'd like to share! Who else?


👨🏽‍💻 By 🐘 @[email protected] 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

Future of Coding Weekly 2025/12 Week 1

2025-11-30 22:19

📢 Announcing Unison 1.0 📄 Towards Pen-and-Paper-Style Equational Reasoning 🧑‍💻 Tom Larkworthy go brrr

Two Minute Week

🗨️ Tom Larkworthy

🧵 conversation @ 2025-11-30

I have written a userspace hook to intercept all code changes in the Observable Runtime, which allows point-in-time recovery by rewriting the cells to be the same as in the past. Furthermore, its a building block towards serializing and replaying the history from IndexDB, so you don't lose changes if you refresh and/or forget to export to file.
Its cool that can be done from userspace, a year ago I felt history might be a challenge, but no!

🎥 Change History

Share Your Work

🗨️ Dennis Hansen

🧵 conversation @ 2025-11-30

🎥 Calculator go brrr

DevLog Together

🗨️ Tom Larkworthy

🧵 conversation @ 2025-11-24

Been working on a different Agentic AI concept, but the Agent is under performing and coding and its not actually useful (unlike robocoop-2 which is good).

Switched to getting a nice way to remember state. Using IndexDB to persist across page refreshes and mutable FileAttachments to carry state between exports (localState).
Brought in ProseMirror to make a notion-like directly editable markdown interface (markdownInput), because its quite annoying to have to write markdown using a programming language and I want to write more in Lopecode.

🎥 Markdown Input

🗨️ Tom Larkworthy

🧵 conversation @ 2025-11-30

I forgot you can shadow Observable Runtime standard functions. So I redid the markdown editor. Its not a distinct function anymore, it overloads the md library function which means it applies to existing notebooks. It serializes modifications as code changes, so there is no difference in representation to the existing markdown.
The reason I implemented this was someone said they expected to be able to edit prose like in Notion, and I do personally feel the Observable experience is not great for the documentation part, as you have to write it in code which located in a different part of the UI to the bit your are reading, which is not natural. Inline editing feels much better. Very happy this can be achieved in userspace without any architectural changes and is backwards compatible to what has already been written.

🎥 inline edit

Thinking Together

🗨️ Tom Larkworthy

🧵 conversation @ 2025-11-26

Dennis Hansen Great workshop on Artifact. I recognized the situation where you have to synchronise updates to do their thing before letting the outer thing tick on. Its in this notebook which is also a dataflow graph based programming environment but that is not graphical
https://observablehq.com/@tomlarkworthy/flow-queue

It interesting seeing the same thing manifest. I think its because values propagate through the program asynchronously, but you sort of want functional reuse or recursion, but calling a function actually takes time now in the async world, so to get that "request/response" functional interface you need the converter from async to sync, which involves a synchronisation barrier to bring back the functional abstraction. After trying to work with it a while I sorta decided its annoying for some problems. The nice thing about a function call is the caller is stopped until the the call finishes, and the result is wired back to the caller, although many different places may make a call to the same function. Its harder to do on a static dataflow graph.

I think the functional calling primitive is something you could probably put into to your cells as they have routing ability (remember who sent me a value and next time I get a value send it back to the initiator?).

I share coz sometimes seeing the same thing in a different context can give helpful for perspective. See your work made me thing about the fact I put a queue in my flow-queue which makes it kinda of an actor too, even though the underlying dataflow paradigm of Observable does not have queueing between cells. I had to add the queue to get to the functional interface, to be able to process one thing at a time on the static dataflow graph 🤔

🗨️ Medet Ahmetson

🧵 conversation @ 2025-11-26

What do you guys think? About a project run by multiple online communities, each responsible for some aspect or feature. For example, right now, I'm working on a gamified collaboration platform. And instead, keeping the leaderboard of the most active users on platform, maybe contact specific organizations who already does it. If I will add the admin panel, and they handle it on the platform.

Linking Together

🗨️ Eli

🧵 conversation @ 2025-11-25

EGG, from "Towards Pen-and-Paper-Style Equational Reasoning in Interactive Theorem Provers by Equality Saturation"

📷 Screenshot 2025-11-25 at 1.08.38 PM.png

🗨️ shalabh: 📢 Announcing Unison 1.0

🧵 conversation @ 2025-11-26

Unision 1.0 released: https://www.unison-lang.org/unison-1-0/
Key ideas are ‘content hash’ identifies functions and code lives in a DB.

📝 Announcing Unison 1.0

After years of engineering, design, and community collaboration, we're excited to release Unison 1.0. This version delivers a refined programming workflow and a mature toolchain. Join us as we celebrate this milestone and look ahead to the future of Unison.


👨🏽‍💻 By 🐘 @[email protected] 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

Future of Coding Weekly 2025/11 Week 4

2025-11-24 11:33

🎙️ TodePond and Dave Ackley 🎼 Thuja: Algorithmic composition with Csound 🧑‍💻 OpenAI constrained generation with Context‑Free Grammar

Share Your Work

🗨️ Mariano Guerra: 🎥 Visual WebAssembly Demo: A Structure Editor for Wasm Modules

🧵 conversation @ 2025-11-18

Demo of a prototype I'm working on to play with structure editors and ways to make WebAssembly easier to understand.

Visual WebAssembly Demo: A Structure Editor for Wasm Modules

🗨️ Mariano Guerra: 📝 A WebAssembly interpreter (Part 1)

🧵 conversation @ 2025-11-20

We build up a simple interpreter from scratch, in JavaScript, for a small subset of Wasm instructions (arithmetic and comparison).

Implementing a Wasm Interpreter to explore its design and semantics

A WebAssembly interpreter (Part 1)

🗨️ TodePond: 🎙️ TodePond and Dave Ackley

🧵 conversation @ 2025-11-20

hi everyone i recorded a podcast episode with Dave Ackley where we talk about robust first computing and jamming
https://www.pastagang.cc/podcast/runrecord.mp3

DevLog Together

🗨️ Charlie Roberts: 📝 teeny

🧵 conversation @ 2025-11-17

on a related note to what Mariano Guerra posted, here’s a little editor library I made using css highlights https://codeberg.org/charlieroberts/teeny

simple demo: https://charlieroberts.codeberg.page/teeny/demos/js/
demo in a wasm audio playground: https://gibber.cc/genish/playground/

A small code editor for live coding performances

teeny

🗨️ Ben: 🎼 Thuja: Algorithmic composition with Csound

🧵 conversation @ 2025-11-19

I've been iterating on docs and implementing a realtime / livecoding interface in my algorithmic composition library Thuja. I can actually do a live session now 🙂 but as I practice with the interface I find ways to improve it, so it's still in major flux.
I'm searching for the right tone in the docs - the readme seems simplistic (musically) to me - next step for me is to walk through some of my pieces cookbook-style, laying out more elaborate use cases.

Thinking Together

🗨️ maf

🧵 conversation @ 2025-11-17

Cooking recipes are like little algorithms. One of my friends made a UI mockup for a visual recipe design tool. It was done for a game, but maybe something like this could be used for regular algorithms. Sharing for inspiration.

📷 cooking_simulator_ui.jpg

🗨️ guitarvydas: 📝 Show Don’t Tell

🧵 conversation @ 2025-11-22

Can we extend the definition of structures, like @dataclass in Python, to include links to .png (and .svg?) files? Then, use IntelliSense to show the picture? Something like this

Show Don’t Tell

AI

🗨️ Tom Larkworthy

🧵 conversation @ 2025-11-17

Oh OpenAI finally offered constrained generation e.g. supply the regex the output should match (something llama.cpp had). I get much better results for coding LLM if the output is XML, so now I can have a custom too output valid XML trivially.

🧑‍💻 OpenAI constrained generation with Context‑Free Grammar


👨🏽‍💻 By 🐘 @[email protected] 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

Future of Coding Weekly 2025/11 Week 3

2025-11-17 00:35

📝 Explorable explorable explanations 💡 SYNIT: a reactive operating system 📝 Open Source Power

Share Your Work

🗨️ Murat Kasimov:

🧵 conversation @ 2025-11-12

Hello everyone! I was discovering how documentation for a programming language could look like - I came with my own engine for Я where you can click on every token in code snippets and follow it. As a demonstration, there are first 6 chapters on polished step-by-step tutorials demonstrating designing a command line task manager: https://muratkasimov.art/Ya/Tutorials/. And here is an example with deconstructing an regular operator: https://muratkasimov.art/Ya/Operators/kyokl/.

🗨️ Nilesh Trivedi: 📱 Qwikbuild AI - Build your App in 7 minutes on WhatsApp

🧵 conversation @ 2025-11-12

Hey folks, this is what I have been working on for past few months: https://qwikbuild.com

The way I like to explain this to technical folks is: it is an AI coding agent not for you but for your friends and family members who likely are mobile-native, and tend to have much higher expectations from AI when it comes to building ready-to-use and full-featured web apps. 😀

Feedback and brickbats are welcome! 🙏

📱 Qwikbuild AI - Build your App in 7 minutes on WhatsApp

Turn your creative ideas into professional websites and apps instantly. Send a voice note, screenshot, or example via WhatsApp, and our AI builds your site in minutes with stunning precision. No coding required.

Qwikbuild AI - Build your App in 7 minutes on WhatsApp

🗨️ Konrad Hinsen: 📝 Explorable explorable explanations

🧵 conversation @ 2025-11-13

Here's a blog post placing my HyperDoc project in the context of Bret Victor's "explorable explanations", with Micrograd supplying the illustrations: Explorable explorable explanations

DevLog Together

🗨️ Mariano Guerra: 🎥 Performant Syntax Highligting with CSS.highlights API and OhmJs

🧵 conversation @ 2025-11-14

Quick overview showing how to generate small and performant syntax highlighting for your own programming languages using OhmJs and the new CSS.highlights API

🎥 Performant Syntax Highligting with CSS.highlights API and OhmJs

Performant Syntax Highligting with CSS.highlights API and OhmJs

Linking Together

🗨️ Jasmine Otto:

🧵 conversation @ 2025-11-11

New public release of Apptron, a local-first IDE and Linux environment.
https://github.com/tractordev/apptron/releases/tag/v0.5.0

Apptron is the first of a new category of general-purpose compute platform with over 5 years of R&D behind it. In these early releases, Apptron is starting out as a humble, local-first IDE. It is a development environment powered by Wanix, a new Plan 9 inspired runtime for WebAssembly, which allows you to run Wasm and x86 programs in a full Linux environment that works entirely in the browser without cloud compute.

🗨️ shalabh: 💡 SYNIT: a reactive operating system

🧵 conversation @ 2025-11-13

Found this evolution of the syndicated actors model: https://synit.org/

an experiment in applying pervasive reactivity and object capabilities to the System Layer of an operating system

Interesting stuff, specially if you ever found actors, tuplespaces, or reactive models interesting. You can see a summary of the syndicated actors here: https://synit.org/book/syndicated-actor-model.html

🗨️ Ivan Reese: 📝 Open Source Power

🧵 conversation @ 2025-11-14

This is a good read about how to interpret what is meant by "open source"

Pullquote:

This definition of open source prohibits discriminating against megacorps and nazis. That's a problem for me.

📝 Open Source Power

We have to talk about open source licensing.

Open Source Power


👨🏽‍💻 By 🐘 @[email protected] 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

Future of Coding Weekly 2025/11 Week 2

2025-11-10 11:53

🧠 micrograd 🎥 I am not dead yet 📝 The Hidden Gem in S/SL: Why Dataless Languages Matter

Share Your Work

🗨️ Konrad Hinsen: 🧠 micrograd

🧵 conversation @ 2025-11-03

Micrograd: a pedagogical implementation of neural networks using a reverse-mode automatic differentiation engine.
https://hyperdoc.khinsen.net/94FE4-micrograd

I have written this as a real-life example of explorable explanations in HyperDoc, my framework for explainable software systems which I demoed at a meetup earlier this year. The main new features in the platform that are showcased are interactive tools and much-improved playgrounds for free exploration.

Feedback welcome at https://codeberg.org/khinsen/micrograd (the source code repository), or right here of course.

📝 micrograd

A tiny scalar-valued autograd engine and a neural net library on top of it

micrograd

🗨️ Ivan Reese: 📝 The Hidden Gem in S/SL: Why Dataless Languages Matter

🧵 conversation @ 2025-11-08

New blog post: 📝 The Hidden Gem in S/SL: Why Dataless Languages Matter

Excerpt:

In this article, I want to discuss my main inspiration from S/SL—a 1970s compiler construction language that most programmers have never heard of, but which demonstrates something fundamental about separating architectural thinking from implementation details.
What is S/SL?
S/SL stands for Syntax/Semantic Language. It was designed for writing compilers—specifically the parts that parse input, analyze semantics, and generate code.
Here’s what makes it unusual: S/SL has no data definitions. You can’t declare integers, strings, arrays, or records.

🗨️ Tom Larkworthy:

🧵 conversation @ 2025-11-08

Kartik asked at some point whether Lopecode could do offline note taking. Sort-of but you would have to remember to export every change or lose you notes and the frequent exports would generate a new file every time cluttering the HDD up.

So I have made a note-taking app that uses IndexDB via dexie.js to remember the work in progress. If you have two tabs open the notes are synced in realtime. The Notes in indexdb are carried forward on export as an inline file attachment to the single HTML file application.

Export now support themes so this is the first dark mode version 👻. Its looks amazing now (CSS taken from ISC licensed NotebookKit and credited).

Obviously if you use it from the web link it will use network so if you wanted to use it you would click download and use it from your computer for true offline. Tested in Chrome/Firefox/Safari and works, but Safari might delete the indexdb data after 7 days (maybe not though if its a file:// ?) There is a technical overview inside the notebook as its meant for demonstration over actual utility
https://tomlarkworthy.github.io/lopecode/notebooks/@tomlarkworthy_notes.html

sidenote: I wrote this slack message earlier in the day, decided not to send it coz there was a bug, recorded the draft message in notes, fixed the bug and pushed, and now the Github.io one now has this very slack message. I kind of like it coz its like an intro anyway, but a bit of a risk for me who publishes notebooks that I might accidentally transmit sensitive information.

🗨️ TodePond: 🎥 I am not dead yet

🧵 conversation @ 2025-11-09

hello everyone i gave a talk about live programming, and what "liveness" means

🎥 I am not dead yet

I am not dead yet

Thinking Together

🗨️ Ivan Reese:

🧵 conversation @ 2025-11-06

What are the all-time great projectional / structure editors? I'm particularly interested in:

  • tight focus on a specific language
  • really good autocomplete / hinting (ie: type-aware, don't show me unhelpful stuff at all)
  • pulling far away from the feel/experience of raw text typing, pushing toward "press a button, out comes exactly the program you wanted"

🗨️ josharian:

🧵 conversation @ 2025-11-06

An esolang idea that might (?) be fun to kick around.

The idea is to take advantage of the fact that LLMs are somewhat resilient in their inputs (can ignore typos, infer intent, etc.) to have a multi-level language.

Here’s a sketch, but I’m not wedded to any of it:

Programs are UTF-8. Each input code point is interpreted as an opcode. (Many opcodes are no-ops, probably most non-ASCII code points.) Some opcode(s) cause LLM execution of the program text.

The fun is writing a program whose opcodes do something useful, while still being natural-language-interpretable enough to use the second-level interpretation of the language as well.

(For the no-LLMs crowd, a similar idea is to have a pixel-based programming language…but the input is always pixels from rendering a textual program. Then you can execute either the pixels, or the text from which the pixels result, and bounce between the two.)

🗨️ Ivan Reese:

🧵 conversation @ 2025-11-08

On Mastodon, maf shared the following discussion prompt:

[at 32m in the talk Hackover 2025 - Patterns in Chaos: How Data Visualisation Helps To See the Invisible, the speaker yote]…

brings up an interesting thought re readable visual design - that visualizations should encode the important variables using features that we've evolved to recognize instantly - on the most primitive level. The example given is rather simple: large vs small... But if we pull this a little further, it might lead us to some interesting, totally not explored visualizations:

  • using familiar vs unfamiliar faces as data points
  • using movement (especially movement of complex foreground against complex background) to highlight key area
  • proximity (stereoscopic images) - this could be combined with movement, so that important points move back & forth
  • we're really good at predicting trajectories of thrown objects - can this be utilized somehow?

Linking Together

🗨️ maf:

🧵 conversation @ 2025-11-04

I didn't expect that. At first sight it seemed to be AI generated but under further inspection turned out to be totally legit. Nice find.

The linked page lists a couple innovations that are introduced. Domains & overlaps is an interesting technique that blends static & dynamic typing. "Memlets" provide a primitive for maintaining state. A simple, universal & also flexible mechanism for merging multiple concurrent processes back into a single thread of execution... Something tells me that the author has some experience working with dataflow languages and is addressing the main pain points.

There is also a PDF with a spec of the language that can be downloaded for free from a couple online stores. I've scanned through it quickly.

It's a fairly technical academic approach that starts with a definition of a language.

It's also pretty comprehensive - covers semantics, execution model, graphical display, programming interfaces. IMO such a priori design doesn't work well in visual space. It's hard to predict what elements will turn out to be annoying and which will create unexpected synergies. But if this language gets actually implemented and undergoes a couple iterations... Who knows... I'll be watching it's development with great interest!

🗨️ Christopher Shank:

🧵 conversation @ 2025-11-04

"Disability Driven Development" from the Damaged Earth Catalog

Disability Driven Development (DDD) is a practice that reimagines computing from a disabled perspective, challenging its seemingly seamless and stable hegemonic operations. It asks who is left out of creating (and joyfully using) digital technology, and how this can be changed. It is a practice by and for those who did not get to shape computing to meet their needs.

Currently computing is stuck in a catch-22: while nobody is better qualified to create access solutions than disabled people themselves, systemic oppression and exclusion result in a situation where those with access needs rarely have the resources to envision or implement those solutions. The history of disability justice demonstrates an abundance of curb-cut effects—situations where focusing on access for one group, yields ideas, changes and solutions that are beneficial to many more people than those in the group the changes were originally meant for.

DDD addresses barriers of access to programming, which relies heavily on text, specifically the English language and the Latin alphabet, with specialized 'languages' that are structured in very specific ways. If that weren't enough of a barrier, the programming world deals with a deeply entrenched bigotry. The resulting lack of access to programming reduces the quality of software, since the creativity involved in thinking about computing through a disabled and trans*computational lens is excluded, denying disabled and other people the quality of life that software could help them achieve.

🗨️ Mattia Fregola: 👾 Dithering - Part 1

🧵 conversation @ 2025-11-09

Great virtual story on dithering

Understanding how dithering works, visually.

Dithering - Part 1

Present Company

🗨️ Daniel Harris:

🧵 conversation @ 2025-11-06

MozFest Barcelona 2025 November 7-9! Anyone from Festival Of Confusion (that's here/us/we!) attending MozFest? Let's meet up! And if not MozFest what events are you attending over the next 6 months? That's 2 questions in one thread: hence the Confusion! 😉


👨🏽‍💻 By 🐘 @[email protected] 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

Contents © 2026 Mariano Guerra - Powered by Nikola