βοΈ Not subscribed yet? Subscribe to the Newsletter
Future of Coding Weekly 2023/11 Week 4
2023-11-26 23:26
πΌ Spreadsheets & Small Software π Lua Carousel πΊοΈ Embark: Dynamic documents for making plans
Two Minute Week
π₯ Wrap and unwrap expression via U03U0SCU5LH
Last week I worked on Wrap / Unwrap Expression. See description under video. (no audio)
Btw. if somebody has a better verb instead of wrap.. let me know.
Our Work
πΌ Spreadsheets and Small Software via Prabhanshu Gupta
Iβve been researching spreadsheets and writing one for a couple months. I wrote a bit about the what and the why, give it a read!
blog.nilenso.com/blog/2023/11/10/spreadsheets-and-small-software
I wasnβt able to cover many specifics here β writing about the work seems like a lot more work than doing the actual work π . Thereβs a lot to cover and Iβm hoping to get to it slowly. Until then please shoot thoughts and questions here, Iβd love to answer.
π₯ Arroost: Normalise sharing scrappy fiddles via Lu Wilson
Watch my new talk!
It's about a music-making node-based language tool for feeling.
ARROOST: NORMALISE SHARING SCRAPPY FIDDLES
π Let's Build a Programming Language via Mike Austin
I've demoed my Kopi language and Rect-Desktop projects a few weeks ago. In my experience writing Kopi, I've always wanted to write a "How to Write a Programming Language" tutorial based on it, since the core language is simple and familiar (infix operators, assignment, anonymous functions, etc.). Here's the start of something (written in Markdown, presented using the React-Desktop Markdown app:
Let's Build a Programming Language
It's in an early draft. I like presenting ideas very incrementally, and being able to see and even interact with each small change. You can modify any of input or parser code and see the result value change.
π Lua Carousel via Kartik Agaram
Lua Carousel: A lightweight programming environment for desktop and mobile devices that you can make changes to while it's running.
repo: git.sr.ht/~akkartik/carousel.love
π₯ Lua Carousel Demo
π¬ Daniel Garcia
Followup on my ~_*Colorful types*_~
project. Iβm trying to create a ~_*map*_~
for a codebase with different zoom levels.
I have been thinking about having 3 zoom levels:
- Level 1: Only colors for both types & functions
- Level 2: Colors and names for types, functions and parameters
- Level 3: Shows the entire source file (maybe with some extra color sugar on top?)
Here are a couple of screenshots of level 1 & 2, and video of the WIP interface.
PS. Anyone have good recommendations of typescript codebases with a couple dozen source code files which I can use for testing?
π₯ Demo
Devlog Together
π¬ Kartik Agaram
More progress on a lightweight programming environment that runs on Linux, Windows, Mac, Android, iOS. Also modifiable live while it runs (though not on mobile devices).
The seed design constraint here was to structurally prevent the pop-up keyboard on a touchscreen from ever blocking my typing. That led to this design of a multi-line commandline editor in the top half, fixing the non-editable output buffer in the bottom half. Independent commands/scripts then expanded in the only other direction available: left/right.
π₯ Carousel Shell
π¬ Kartik Agaram
πΊοΈ Dispatch 001:On Embark and Lude via Duncan Cragg
Hiya, I just read this new newsletter from Ink'n'Switch:
inkandswitch.com/newsletter/dispatch-001
And it says:
Solo independent researchers we know often discuss the challenge of working alone. Being part of a research group can create community, social accountability, provide feedback, and just give you someone to talk to when youβre feeling stuck or bored. This is why we started our Researchers-in-Residence program.
Which made me think "this could be something we set up in FoC!"
And then I came right here to say that, without thinking it through any further...
π₯ Creating html for nodes using gpt4 api in a visual programming system via Maikel van de Lisdonk
Hi, in this weeks video I show a new node type in which a prompt can be entered which is used to create HTML via openai gpt4. It's quite powerful .. the created nodes can receive and visualize input data from another node. This is offcourse inspired by makeitreal from tldraw which uses gpt4-vision-preview. I have been playing with the prompt to get the result that I wanted, although the results are not consistent when recreating the html using the same prompt. Still, very cool that this is possible.
π¬ Kartik Agaram
Achievement unlocked: I've built an app large enough[1] that it crashes my programming environment that puts all the code on a spatial surface.
The problem: I do this snazzy initial animation (see video) that takes in the whole thing before zooming back in somewhere. That animation works by drawing the whole surface to an in-memory canvas before transforming it. Turns out drawing to a canvas still uses the video card, and I don't have enough video RAM for a virtual "monitor" of this resolution.
[1] Or spread out enough. It's not really about lines of code, just how much area the code occupies.
π₯ bf codemap
Reading Together
π¬ Beni Cherniavsky-Paskin
I was leafing through my father's old books when this diagram caught me off-guard.
We're so used now to having an OS with apps, that it's weird to think of OS-level transitions (login->shell), inter-apps transitions (shell->vi) and inside-app transitions (vi's command<->append modes) as similar things. π
But to a user new to computers, yes these are all "modes".
π¬ Janne Aukia
I think that often the most difficult part of programming is debugging: humans aren't very good at "seeing" how an app operated when it failed. You get some log output that might or might not have references to the correct file locations.
I don't see any reason, in the long term, why humans would be better than machines at debugging. How to make that happen? I assume somebody is building this already. Would it help if an AI with a large context window + access to the VM could see the whole call logs/tree and see exactly what is going on? AI could learn from other users, see everything that happens in a run without debugger/console.logs, try multiple solutions in parallel, and fix issues while you sleep.
Thoughts on this?
Content
π Spreadsheets and Small Software - nilenso blog via Benji York
"We wanted tools to make sheds, we got tools to make skyscrapers."
πΊοΈ Embark β Dynamic documents for making plans via Ivan Reese
Ink & Switch just released a new essay: Embark β Dynamic documents for making plans.
Starting from a desire to "unbundle the app" in the name of malleable software, they explore using a bullet-point outliner as a substrate for dynamic properties, computations, and views. They ground the work with a specific use case β trip planning β and they hard-code a bunch of stuff that ought to be pushed into user space, granted. But it's easy to look at this, imagine how it could be expanded, and see some really compelling possibilities for a different way to approach creating and distributing software.
Congrats to Paul Sonnentag, @Alexander Obenauer, and Geoffrey Litt!
π» Pickcode | Make cool stuff with code via Mattia Fregola
Pickcode β a visual language to teach kids to code.
π§Ά There are no strings on me via Justin Blank
An essay on the challenges of image based/live systems: There are no strings on me
π Lua Carousel: create little programs on desktop or mobile devices via Walker Griggs
A saw a friendly face on the front page of lobsters this morning
π₯ Bootstrap yourself into conviviality by writing your own Forth via Kartik Agaram
I just found an absolutely ancient bit of advocacy for convivial tools. From 2008!
via muforth.nimblemachines.com
Jonathan Edwards Were y'all aware of this when you organized 2020.programming-conference.org/home/salon-2020?