Hi, I've been fixing some bugs in my "infinite-canvas based visual interactive programming editor inspired on flow based programming"(yeah that's a lot of words.. playing around with finding a proper sentence to describe it😊) .. you could already edit the program live , make changes and see the results directly.. but there were some scenario's that didn't behave correctly so that the program became "dead" and needed a browser refresh to come alive again..I fixed those... it had todo with resetting the internal flowrunner-engine on wrong moments after making changes to the visual flow: the program now stays alive even if you make bugs. I'll really do my best to make a small video about this soon😊 .. and yeah the strange loop talk by @Jack Rusher was also very inspiring to me, thanks!😎

I’ve been thinking about how to make a domain specific editor for my new job. I’m working on a new JIT compiler for Ruby. It’s fairly well developed, but the tooling around it leaves a lot to be desired. I can definitely use lldb for most of it and do, but it is almost never what I actually want. I’ve been trying to think about how I can make my debugger context-sensitive. The bugs I’m tracking down are almost all, in development bugs. So why not show my code changes instead of every file? As I’m developing, I want to know what difference there is in codegen, why not save output between runs and show me only methods that were affected? I have four stacks that I’m working with, the Ruby value stack, the Ruby control stack, the C stack, and a compile time virtual context stack. What if I could visualize all of these at once?

Ever have one of those days where you realize the thing you are making is very possibly actually a completely different thing? Like, Blawx will allow you to run a query, in the absence of concrete facts, and will find all the various different reasoning paths that could be used to answer that query, and show them to you. If you recombine those explanations using disjunctions, you would have a single decision tree. Invert it, that tree is an imperative function. So... Blawx is maybe a tool for generating imperative code from declarative specifications, where the declarative specification is a law? 🤯

So I largely gave up with webcode to instead seek economic shelter in a Berlin startup (taktile.com). It is still in the FoC camp being an instant decisioning platform with node and wire diagrams, with code nodes, but focussed on a pragmatic vertical (finance decisions like loan applications). Just FYI. Once I am ramped up a bit more I hope to start sharing more on some of the neat features like bringing engineering technology like JSONschema to non programmer risk analysts.

Hi, small update on my infinite-canvas visual programming tool. Improved the handling of excel-like datagrids.. you can now sum or avg a column and/or use it in a (pie) chart.. offcourse cell ranges are also possible. I wanted to prepare a video this week, have been doing some test runs again with obs, but I am not happy yet with the results so a little bit of patient still needed :-) In the meantime, hopefully the screenshots show some of the progress and working of the system.. you can also see the changing of the state of the condition node depending on the input.. although this is better shown in a video offcourse.. (see the comment section of this post for the "error-state")

I woke up this morning and started implementing Potluck for myself. I want this in my toolbox, but a browser is just not convivial enough.

I have so many ideas I want to build that require a text editor. I often feel that if the editing sucks, the whole project just won’t feel nice. But recreating a decent text editor (by this typically mean for code) is always a reasonably big undertaking. What I’ve started working on is a headless editor. There are some that exist like xi, but I’m aiming for something a bit simpler. Right now I’m dealing with proper cursor and multi-cursor support. I’m going to be working on a few implementations for textbuffers. Going to add treestyle undo and redo. Going to get syntax highlighting working. What features would you want in a library like this?

I'm tugging on this thread today. Pensieve's 2D surface isn't actually very good at giving me a sense of space like say https://www.inkandswitch.com/capstone. I just spent some time trying to cross-link stories far apart in space and blowing my stack, copying ids laboriously into a scratch space outside pensive, then pasting it into hyperlinks in the right place in pensieve. Then I realized, I should just use new kinds of links. The value of hyperlinks is when they're inline, whereas links just line up at the bottom of each note. But I currently can't linkify arbitrary text anyway. (Potluck style automation might help me get there.) For now, links are the best way to do hyperlinks in Pensieve. I also get back-links for free.

Hi, I've been working on enabling crud operations in combination with calling api's that my visual programming editor doesn't know about (I've used supabase).. the only really new Node-type that I made is a generic data-table which can be configured in the flow-editor. The data-table gets automatically updated after doing delete/update/create operations. To give an impression, here's a screenshot:

Some progress on a structure editor for my natural language (business) logic programming environment. I'm actually building a structure editor generator so vast majority of the work has gone towards that rather than implementing language features. "type checking" for the function/predicate "self/this/it" argument is not implemented yet on the video, so the editor allows calling the functions in wrong places.

I've been working on a viewer for behavior of YJIT (the ruby JIT I work on at work). It is very early, but I figured I'd share what I have so far. Here's a little gif of it currently. Right now, I capture more data than I display. I also have more data I need to capture. I built this view with rust and skia. It has worked out pretty well. What doesn't work that well is graphviz for graphs. There are so many interactive things I want to do with graphs and graphviz just isn't cutting it. What you are seeing is all the ruby methods (grouped by files) that we compiled. The little graphs next to each method are the blocks we compiled. Their width is relative to the size in bytes of the disassembly of the machine code. Red nodes are exit nodes.

2022 Advent Of Code Solutions, Day 1, Thread:

Advent of code day 1, using the visual programming editor that I am building (I needed to implement a new node-type "operator" first☺️)

2022 Advent of Code Solutions, Day 2, Thread:

2022 Advent Of Code Solutions, Day 3, Thread:

A simple enough C++ solution; it's much easier in Python

Could you add the link to the challenge each day? I know, I could Google it, but it would be really handy and could boost engagement with the AoC in this community!

I found these links, but there are many results in Google: https://adventofcode.com/2022/day/1 https://adventofcode.com/2022/day/2 https://adventofcode.com/2022/day/3 .. is that correct?

2022 Advent of code day 4 part 1 using my visual programming environment

2022 Advent of Code Solutions, Day 4, Thread:

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!

2022 Advent of Code Solutions, Day 5, Thread:

Less about the solution, more about the process... I streamed solving the first 2 days of AoC with WhiteBox here: https://www.twitch.tv/videos/1669247002 I should be doing more soon!

Does anyone else find switching code languages as daunting as I do? I always dread it like I'm trying to cut off a limb, or something. Just spent a week doing HTML/CSS, now back to Prolog.

there is switching languages and then there is switching from HTML/CSS to Prolog 😄

2022 Advent Of Code Solutions, Day 6:

2022 Advent Of Code Solutions, Day 7:

I over engineered the solution today, but it worked well enough.

It would have been simpler with a dictionary; I just expected part 2 to be harder than it was.

Advent of Code, Day 8: