Future of Coding Weekly 2022/04 Week 1

[marianoguerra]

• [x] Change Month and Week Number

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

• [ ] Summary

• [ ] Hashtags

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

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

• [x] Update Search Index

• [x] Download New Attachments

• [x] Update links

• https://tinyletter.com/

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

• http://localhost:8000/history/

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

• https://stackedit.io/

[marianoguerra]

✍🏻 Drawing Dynamic Models 🖱️ UIs by Example 🎼 Code Dynamic Music 🥼 Static Analysis at GitHub

Our Work

🎥 Wheel - Tutorial via xyzzy

🧵 conversation

I have been dogfooding my literate programming tool wheel. So far I have been able to develop multiple webapps, a game and even a C++ based desktop app with it. I also think LP can be invaluable in managing your programming notes and system admin commands, not to mention writing html based books. You can checkout all the project links here.

I dub my approach to LP as procedural literate programming. Instead of developing new syntax, I use string substitution based approaches common in web development which is more flexible than all the other approaches to literate programming so far, including the original cweb.

🧵 read more

[marianoguerra]

✍🏻 Crosscut: Drawing Dynamic Models via Szymon Kaliski

🧵 conversation

hey everyone, check out this programming-and-drawing exploration we worked on together with Ivan Reese and Marcel Goethals at Ink&Switch a couple of months ago - inkandswitch.com/crosscut/

[marianoguerra]

🖱 Peridot: Creating User Interfaces Using Programming by Example, Visual Programming, and Constraints (1987) via Mariano Guerra

🧵 conversation

📝 New post in the "History of No-Code" series

[marianoguerra]

💻 Tofu via Gregor

🧵 conversation

Hey muchaches, I've been quietly consuming the newsletter&podcast these months...errr..years (thankslots Steve, Mariano, Ivan and all of you for the inputs+inspiration!) while slowly working on my side-project: Tofu. When thinking of this community, I always place Tofu as more of an attempt at the near-future-of-programming. It does not aim for revolution as much as many of the cool things here (booo incrementalism boo boo).

Anyway, after years of working on it and using it on my own, I want to slowly start letting people in and this community is prime for me there. It is currently an experimental extension for VSCode for structurally yet fluidly editing JS & TS. If you don't have VSCode installed, you can also use it within your browser here (there should be a pop-up asking if you want to install the Tofu extension). If you do have VSCode, here's a link to the extension in the marketplace.

[marianoguerra]

Thinking Together

💬 Mariano Guerra

🧵 conversation

Is there a "grammar/pattern/algebra of parser combinators" somewhere?

Something that describe the common parts that most parser combinators have, choice, iteration and so on

[marianoguerra]

💬 Mark Dewing

🧵 conversation

I'm interested in using call graphs/control flow in a hierarchical way to understand programs better. The problem is there seems to be two extremes - high level diagrams done manually and low level call graphs generated by tools. A manual drawing with boxes and arrows is often used when describing a program at the highest level. While it works, one question is how to move to the next level of detail? Someone has to do that manually as well. These diagrams aren't connected to the source and can get out of date. The structure is going to change slowly at the highest level and so keeping up-to-date manually isn't that much trouble. More detailed levels, though, can change more frequently and keeping them up-to-date is more work. At the other extreme, tools to generate callgraphs give all the functions. They can filter by time, number of calls or call stack depth, but those doesn't necessarily correlate to what's important conceptually. I'm wondering if there's any work on anything between these two extremes? Both in generating it and visualizing it. (Searching online for 'hierarchical call graph' gives research on automated and machine learning approaches to discovering a hierarchy - interesting as research, but not what I'm after here. I would prefer something manual like adding program annotations or creating filtering terms - something that can be automated as part of a build or CI process.)

[marianoguerra]

Content

🎼 Strudel: write dynamic music pieces in Javascript via Mariano Guerra

🧵 conversation

With Strudel, you can expressively write dynamic music pieces. It aims to be Tidal Cycles for JavaScript (started by the same author).

[marianoguerra]

🎥 "Tree-sitter - a new parsing system for programming tools" by Max Brunsfeld via Mariano Guerra

🧵 conversation

[marianoguerra]

❓ Rego: Datalog inspired Policy Query Language via Mariano Guerra

🧵 conversation

Rego was inspired by Datalog, which is a well understood, decades old query language. Rego extends Datalog to support structured document models such as JSON.

Rego queries are assertions on data stored in OPA. These queries can be used to define policies that enumerate instances of data that violate the expected state of the system.

[marianoguerra]

📝 Static Analysis at GitHub via Shubhadeep Roychowdhury

🧵 conversation

[marianoguerra]

🐦 Tweet from @meekaale via dnmfarrell

🧵 conversation

Love this arrangement for s-exprs

🐦 Mikael Brockman 🥸: new user interface paradigm just dropped

[marianoguerra]

🐦 an accessible game making tool for phones via Joe Nash

🧵 conversation

🐦 v buckenham: announcing my new project: Downpour

an accessible game making tool for phones

there's a landing page & an email signup here: https://downpour.games/ and a blog post: https://v21.io/blog/announcing-downpour and here's an early screenshot:

[marianoguerra]

📝 Lay-it-out: Interactive Design of Layout-Sensitive Grammars via Alexander Chichigin

🧵 conversation

Fengmin Zhu, Jiangyi Liu, Fei He

Layout-sensitive grammars have been adopted in many modern programming languages. However, tool support for this kind of grammars still remains limited and immature. In this paper, we present Lay-it-out, an interactive framework for layout-sensitive grammar design. Beginning with a user-defined ambiguous grammar, our framework refines it by synthesizing layout constraints through user interaction. For ease of interaction, a shortest nonempty ambiguous sentence (if exists) is automatically generated by our bounded ambiguity checker via SMT solving. The soundness and completeness of our SMT encoding are mechanized in the Coq proof assistant. Case studies on real grammars, including a full grammar, demonstrate the practicality and scalability of our approach.

[marianoguerra]

💻 Mito via yeT

🧵 conversation

trymito.io reminds me of some of the early episodes covering stream sheets, the spreadsheet paradigm always seems to crop back up

[marianoguerra]

📝 Rethinking Visual Programming with Go · divan's blog via Shubhadeep Roychowdhury

🧵 conversation

[marianoguerra]

https://tinyletter.com/marianoguerra/letters/future-of-coding-weekly-2022-04-week-1