✉️ Not subscribed yet? Subscribe to the Newsletter

Future of Coding Weekly 2024/01 Week 5

2024-01-28 22:46

📍 Spatial Computing 🧑‍🏫 Future of Kids Coding

Our Work

📝 Structured data. Not too much. Mostly text. via Kartik Agaram

🧵 conversation

📍 Spatial Computing with links not apps via Duncan Cragg

🧵 conversation

My latest article:

Spatial Computing with links not apps

Freedom from the Metal to the Metaverse

Devlog Together

💬 Jason Morris

🧵 conversation

This week I paid off some technical debt, and refactored a single 7500-line file into 134 different JavaScript modules. I did this to myself. No one to blame but me. But it's finished.

Thinking Together

💬 Mariano Guerra

🧵 conversation

Why aren't you using one of these? What's missing in them? is your use case not covered?

gtoolkit.com is the Moldable Development environment. It empowers you to make systems explainable through experiences tailored for each problem.
unison-lang.org A new approach to Distributed programming
github.com/hyperfiddle/electric A reactive DSL for full-stack web development, with compiler-managed frontend/backend network sync
redplanetlabs.com a new programming platform that ** reduces the cost of building scalable backends by 100x
croquet.io Multiplayer Platform for Web and Unity
enso.org Nodes and wires data manipulation
rvbbit.com reactive data boards & flows
wolfram.com/language a symbolic language, deliberately designed with the breadth and unity needed to develop powerful programs quickly.

💬 Jacob Zimmerman

🧵 conversation

Just curious for all your thoughts, is being ahead of your time a good thing? I’m thinking of a conversation I had with @Toby Schachman in the Cuttle discord a while back where he mentioned that Cuttle aimed certain details at a status-quo of programming style unlike it’s predecessor Apparatus, I thought that was quite profound. I’m thinking also of Fortran vs Lisp (or perhaps Forth). When is it not worth it to meet people where they are?

📍💬 Eli Mellen

🧵 conversation

I wanted to bounce 2 terms I've been thinking of off of this group:

I dig visual programming, but think the term is like a little bit of a brain poison because it isn't really descriptive of the goals, and, like, almost all textual programming is inherently visual, too...just...in the way text is.

I think Ivan Reese was the person I first heard float the term "spatial programming," which I dig, but at least for me, it also misses the real value add of what I'm looking for in a "visual" system.

So, the two terms I've been kicking around:

relational programming
cartographic programming

Neither are perfect, and both feel exhaustingly pretentious (a good thing, may haps?) but my intention with both terms is to highlight that these sorts of systems, unlike text-based programming, help make the relationships between different elements (classes, data flow, inheritance, etc.) meaningful using information other than similar names.

Useful? Stupid? Prior art?

Content

🎥 The Only Unbreakable Law via Konrad Hinsen

🧵 conversation

Youtube Thumbnail

A nice talk about Conway's law

📝 Visualization of Cultural Heritage Collection Data: State of the Art and Future Challenges via Jasmine Otto

🧵 conversation

Given recent discussion of what social scientists need from computing (and is it plain-text scripting?), sharing this recent survey of cultural heritage visualization systems (16p). Section 3.4 (Granularity and Interactivity) will be especially interesting; the authors avoid flattening this idea to a 'file system'.

💬 Eli Mellen

🧵 conversation

Another one of those developer thriving comics from pluralsight’s research folks. I like that this one hits on contest culture, and its relationship to AI. (also, love that the PDF includes accessible text)

📄 Brilliant Blobs.pdf

🧑‍🏫🎥 Testing a new programming approach with 11 and 12 year-old children by Agustín R. Martínez via Beni Cherniavsky-Paskin

🧵 conversation

Youtube Thumbnail