Adding parallel execution will make it true 2D at execution time. Even though it's sequential code. More over it can be logically, architecturally 2D while being 1D from interpreter's standpoint. If it uses cooperative multitasking with 1 running task at a time. Or simply 1 core processor.

Recto, by contrast, makes two dimensions part of the syntax itself: elements and rects can expand horizontally or vertically, and they can nest recursively. That's the difference I wanted to highlight.

sheet music isn't a language, it's a notation. it's just a concise way to represent a waveform (a song). and it's certainly one dimensional because you either play the song forwards or backwards.

The other meaning of "recto" is used only in medical literature or in mean jokes where you pretend to talk seriously.

I worked with teachers of other countries of Latam, sometimes in geometry problems for children. For example, it's usual "ángulo recto". I don't have it in my list of taboo or problematic words.

For example a kite-like cuadrilateral has a different names in each country, none in offensive, but you must be very cautios to ensure everyone understand the same meaning.

Also, ur kids dont understand am/pm that is usual in other countries. To avoid problems everything must be between 1:01 and 11:59.

> 2003

> PATH is a programming language that is similar to Brainfuck. This intuitive language requires a simple grasp of two dimensional space, one requirement that almost no other programming languages have.

[1] https://sourceforge.net/projects/path/

[2] https://pathlang.sourceforge.net/

A time paradox from [2]:

  create x = 10;
  time point;
  print x; //prints 10 in first timeline, and 20 in the next

  create traveler = 20;
  traveler warps point{
      x = traveler;
      traveler kills traveler;
  };

[2] https://www.reddit.com/r/ProgrammingLanguages/comments/1golf...

It's also worth checking out Extempore[1] by Andrew Sorensen and Ben Swift, which grants you have incredibly precise timing semantics at the sample level.

"Each extempore process has a scheduling engine built-in, allowing tasks to be scheduled for execution at a precise time in the future. Unlike threading constructs such as sleep() or wait(), which don’t provide strong guarantees about temporal accuracy (i.e. the time they’ll sleep/wait for), Extempore's scheduling engine is guaranteed to execute its tasks at the requested time (the number of audio samples since Extempore was started). This temporal guarantee is significant for time critical domains such as audio and graphic, and real-time systems programming."

What's cool about this is that you're able to modify the program while it's running, and only update sections of it at a time, using the editor as a scratchpad, and it supports networking so you can precisely synchronize a herd of non-local devices and do things you'd have an extremely hard time doing in other languages. The applications extend far beyond just audio and visual programming.

What both of these languages have in common is that they are designed for live coding, or as Sorensen says, cyberphysical programming. I am very interested in the marriage of these technologies and recent transformer models.

[0] https://100r.co/site/orca.html

[1] https://extemporelang.github.io/docs/overview/time/

https://www.i-programmer.info/babbages-bag/325-mcculloch-pit...

It does so by creating instant connection between events across large distances.

Its inerrant parallalelism makes it also possible to do pretty complex evaluation on large canvases.

Maybe not exactly, but there was one task[1] in ICFPc 2024[2] where you create programs that are laid out in 2D, and there is a special operator that causes the control flow to travel back in time. It was super fun.

[1] https://github.com/icfpcontest2024/icfpc2024/blob/main/stati...

[2] https://icfpcontest2024.github.io/

There are also experiments into going higher than that: https://esolangs.org/wiki/Category:Multi-dimensional_languag...