Future of Coding Weekly 2022/12 Week 2

[marianoguerra]

• [x] Change Month and Week Number

• [x] focWeekExport "2022-01-19" "2022-01-26"

• [x] Update Search Index

• [x] Download New Attachments

• [x] Update links

• [x] Check that comment links work (push weekly dump with channel summaries)

• [x] Check to mention right person for moved messages

• [ ] Summary

• [ ] Hashtags

• [ ] Set title in newsletter

• https://tinyletter.com/

• https://tinyletter.com/marianoguerra/letters/

• http://localhost:8000/history/

• https://marianoguerra.github.io/future-of-coding-weekly/

• https://stackedit.io/app#

[marianoguerra]

🎙 FoC • Bret Victor • Magic Ink 🎥 Managed Copy & Paste ✍ Live Literate Programming 🔌 Generative Graphics

Our Work

📝 hsm.py vs state.py via Paul Tarvydas

🧵 conversation

An essay about the history of compiler-appeasement languages, meant for discussion.

read more...

[marianoguerra]

📝 How to Think About Compiling via Nicholas Yang

🧵 conversation

Hey all, this blog post has been kicking around in my drafts for a while. I finally decided to complete it. It’s about thinking about compilation, basically the strategies and techniques that I’ve learned in my short time writing compilers. It’s what I wish I had as a resource when I started.

[marianoguerra]

🎙 Future of Coding • Episode 60 Bret Victor • Magic Ink via Ivan Reese

🧵 conversation

Hey, ya'll ever hear of this guy? He posts some wild stuff. Feels like it might be relevant to the folks here. Maybe a little fringe. For instance, he thinks that software could be — get this — better! You might be surprised to learn that I also think software could be better. Radical idea, yes, but it feels like it's finally time for us to take the idea seriously.

Next month, we're reading Peter Naur's Programming as Theory Building, with a little bit of Gilbert Ryle's The Concept of Mind as background.

[marianoguerra]

Reading Together

📗 Live Coding: A User's Manual via Tom Lieber

🧵 conversation

Live Coding: A User’s Manual is out! “A new book about the history and culture of live coding, published by MIT Press and available open access.”

[marianoguerra]

Thinking Together

💬 Jim Meyer

🧵 conversation

Provenance of content will be a huge challenge due to recent advancements in AI/ML. My immediate thought was "but code is in Git etc. and we know the author", but that's all void if the actual author of the code was a tool like ChatGPT/Co-Pilot and the dev was just the one that pushed it.

Maybe AI will be what brings about next-gen versioning systems where content provenance is managed at the AST node level during code authoring, and not just by whoever pushed the code after the fact.

[marianoguerra]

💬 Jan Ruzicka

🧵 conversation

Do computers make a qualitative difference compared to paper and a concentrated human mind?

read more...

[marianoguerra]

Content

💻 github.com/betaveros/advent-of-code-2022 via Chris Maughan

🧵 conversation

The guy at the top of this year's advent of code leader board (by some margin) is using a language he made himself (noulith), which is implemented in Rust (linked on the below page, which shows some of his solutions). It even has a syntax highlighted CLI. Next level for sure. But interesting that he can 'optimize' his chances in so many varied puzzles by having his own language. Of course, maybe he'd be just as fast in Python; but I wonder what there is to learn from his language design, if anything.

[marianoguerra]

📝 Note taking in Emacs with howm via Kartik Agaram

🧵 conversation

Interesting long-tail tool-for-thought

This bit is particularly tantalizing:

There are two kinds of links supported by howm, namely goto and come-from (in a nod to INTERCAL). goto links are forward references and written like this:

>>> howm

Pressing return on this line when howm-mode is enabled will show a list of all occurences of the word howm in your notes directory.

In contrast, a come-from link is written like this:

<<< howm

And this will cause the word howm in any howm-mode buffer to be underlined and trigger a search where the buffer with <<< howm will appear first.

🧵 conversation

[marianoguerra]

💬 Jarno Montonen

🧵 conversation

I just found about intentional software and their language workbench work yesterday. Very secretive indeed, but I found some interesting material. Here's a list in case someone finds these useful:

• The story: martinfowler.com/bliki/IntentionalSoftware.html & Intentional Software bought by Microsoft (ex employee comment in the comments)
• (Only?) public demo of their product: Intentional Software - Magnus Christerson and Shane Clifford
• Apparently Simonyi's team's work while still at Microsoft: Intentional Programming demo (Part 1) - Editor & Intentional Programming demo (Part 2) - Compiler
• Simonyi's talk(s). These are basically the same, I liked the first one maybe a bit better: The Intentional Domain Workbench & Charles Simonyi Keynote at MODELS 2013 Conference
• Their paper (I found this a good read. Should be interesting to anyone interested in projectional editing, generative programming, model driven development, language driven development etc): Intentional software
• Simonyi's paper while still at Microsoft: The Death Of Computer Languages, The Birth of Intentional Programming

[marianoguerra]

🎥 Short demo of Managed Copy & Paste at PAINT'22 via Mariano Guerra

🧵 conversation

Short demo of Managed Copy & Paste at PAINT'22 by Jonathan Edwards

[marianoguerra]

🎥 Live22 prerecorded version : Ampleforth: More than a Live Literate Editor via Mariano Guerra

🧵 conversation

[marianoguerra]

🔌 alma.sh via Florian Schulz

🧵 conversation

Another nodes and wires ui for “generative graphics” by Emil Widlund

[marianoguerra]

📝 Algebraic Effects and Handlers on Desk via Ryo Hirayama

🧵 conversation

I believe that a language feature called “algebraic effects and handlers”, because of their overwhelming simplicity, is a key to make programming more accessible to people. Please read my article about it.

[marianoguerra]

💡 An open-source minimalist computing technology based on the principle “Less is more” via Konrad Hinsen

🧵 conversation

One more software system designed to be minimalist: minimacy.net

There are many ways to be minimalist because there are so many criteria that can be minimized. This one aims for minimal total code complexity within the constraints of being useable for a specific category of code, which is roughly a single server or desktop process. Minimacy is a programming language (strongly resembling the ML family) plus a virtual machine that runs the compiled code. The VM can run on bare metal, or as a process in a host OS. Development happens outside the system. The whole system wants to remain undertstandable in all detail by a single person. So far that's guaranteed by having a single author.

I attended a seminar by it author yesterday, where he discussed many of the tradeoffs made. Sounded quite reasonable.

[marianoguerra]

📝 Systems Software Research is Irrelevant via Jack Rusher

🧵 conversation

An old classic, but I feel like this quote has a place here.

[marianoguerra]

Devlog Together

🎥 Solvng Advent of Code 2022 using Lamdu #5 via Yair Chuchem

🧵 conversation

I had a fantastic experience solving AoC Day 5 using Lamdu!

If anyone has a better environment for doing this, I’d like to know!

[marianoguerra]

💬 Chris Maughan 2022 Advent of Code Solutions, Day 5 🧵 conversation

🎥 I streamed solving the first 2 days of AoC with WhiteBox via Andrew Reece 🧵 conversation

💬 Chris Maughan 2022 Advent Of Code Solutions, Day 6 🧵 conversation

💬 Chris Maughan 2022 Advent Of Code Solutions, Day 7 🧵 conversation

💬 Chris Maughan: I over engineered the solution today, but it worked well enough 🧵 conversation 🗒️ C++

💬 Chris Maughan: It would have been simpler with a dictionary; I just expected part 2 to be harder than it was 🧵 conversation

💬 Chris Maughan: Advent of Code, Day 8 🧵 conversation

💬 Chris Maughan: Advent Of Code, Day 9 🧵 conversation

💬 Chris Maughan: Advent of Code Day 10 🧵 conversation

💬 Yair Chuchem: Advent of Code Day 11 🧵 conversation

[marianoguerra]

https://tinyletter.com/marianoguerra/letters/future-of-coding-weekly-2022-12-week-2