{"id":9328,"date":"2026-05-12T10:17:03","date_gmt":"2026-05-12T10:17:03","guid":{"rendered":"https:\/\/www.dyalog.com\/blog\/?p=9328"},"modified":"2026-05-12T10:42:21","modified_gmt":"2026-05-12T10:42:21","slug":"dyna26-a-review","status":"publish","type":"post","link":"https:\/\/www.dyalog.com\/blog\/2026\/05\/dyna26-a-review\/","title":{"rendered":"DYNA26: A Review"},"content":{"rendered":"<p>In April we hosted <a href=\"https:\/\/www.dyalog.com\/north-american-user-meetings\/dyna26.htm\" target=\"_blank\" rel=\"noopener\">DYNA26<\/a>, our latest Dyalog North America user meeting. We returned to midtown Manhattan for a day of presentations, demonstrations, and the sort of impromptu conversations that only happen when APLers are in the same room.<\/p>\n<p>Part of the Dyalog Ltd contingent (Brian Becker, Rich Park, Asher Harvey-Smith, and Holden Hoover) spent a few days beforehand in Rochester, New York, having a pre-DYNA &#8220;conclave&#8221; at Brian\u2019s house, working through tooling design discussions and event preparation. We&#8217;re a geographically-distributed team, so we make the most of the opportunities to work together in person; our thanks to Brian for hosting once again.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-9449\" src=\"https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_johanna_03-1024x538.jpg\" alt=\"Attendees watch Morten's presentation\" width=\"584\" height=\"307\" srcset=\"https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_johanna_03-1024x538.jpg 1024w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_johanna_03-300x158.jpg 300w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_johanna_03-768x403.jpg 768w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_johanna_03-500x263.jpg 500w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_johanna_03.jpg 1200w\" sizes=\"auto, (max-width: 584px) 100vw, 584px\" \/><\/p>\n<p>The room filled with a familiar mix: enthusiasts, current developers building on Dyalog at customer sites, users of other APL implementations, and a few who hadn&#8217;t written any APL but were curious enough to spend a day with us. As ever, that mix is what makes DYNA enjoyable to host.<\/p>\n<h2>Presentations<\/h2>\n<p><strong>The Dyalog Road Map<\/strong><br \/>\nMorten Kromberg (remote)<\/p>\n<p>Morten joined us remotely to open the day with the road map. The headline theme was LLMs. Stephen Taylor&#8217;s line that &#8220;Claude is the new Quad&#8221; captured it nicely, suggesting how the often-tedious system-interaction layer of programming, usually handled by I-beams and quad-functions and increasingly by libraries, can now be handled by LLMs as well, leaving APLers freer to focus on the core problem-solving to which the notation is so well-suited.<\/p>\n<p>Morten covered recent experiments and experience: writing prototypes, tests and documentation; generating <code class=\"language-apl\">\u2395WC<\/code> GUI code; and producing interactive tutorials for existing tools. There appear to be some productivity gains, particularly when an experienced developer is supervising. LLMs are already strong at non-APL tooling code (C#, HTML\/CSS\/JavaScript) that APLers regularly need to write around their core applications, and they&#8217;re steadily improving with APL code.<\/p>\n<p>Of course, generative tooling is not the only thing on the road map. Morten talked about an increased focus on organisational and software security through the BSIMM initiative, including static analysis of both the interpreter&#8217;s C code and APL code. This can be used to, for example, find injection vulnerabilities through uses of <code class=\"language-apl\">\u234e<\/code> (<em>execute<\/em>), <code>\u2395SHELL<\/code>, or SQAPL. He also covered recent language additions, including APL array notation and <code class=\"language-apl\">\u2395VGET<\/code>\/<code class=\"language-apl\">\u2395VSET<\/code>, and looked ahead to future work including a potential <code class=\"language-apl\">\u2395IMPORT<\/code> module system \u2014 a prerequisite for the robust project and package management that the community has been asking for.<\/p>\n<p><strong>An APL App End to End<\/strong><br \/>\nRich Park<\/p>\n<p>Rich followed with a showcase of Dyalog&#8217;s tools wrapped around a single example application: a video data CRUD\/REST service with search and recommendation. The demonstration included the upcoming Stark REST router and its OpenAPI specification generator, the extensions to <code class=\"language-apl\">\u2395DT<\/code> coming in Dyalog v21.0, and the use of isolates to push heavy computation into a separate Dyalog process so that Jarvis\/Stark can keep servicing HTTP requests in the main thread. He showed APL code to compute search results and recommendations using simplified expressions of term-frequency inverse-document-frequency and cosine-similarity, to convey how using Dyalog to deal with the fiddly interfaces and inconveniences of real applications lets us focus on using APL to express core algorithms. Plenty to consider for anyone building services in APL.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-9450\" src=\"https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_holden_01-1024x538.jpg\" alt=\"Rich pointing to slide of application architecture overview diagram\" width=\"584\" height=\"307\" srcset=\"https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_holden_01-1024x538.jpg 1024w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_holden_01-300x158.jpg 300w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_holden_01-768x403.jpg 768w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_holden_01-500x263.jpg 500w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_holden_01.jpg 1200w\" sizes=\"auto, (max-width: 584px) 100vw, 584px\" \/><\/p>\n<p><strong>Migration Tools for APL Systems<\/strong><br \/>\nMorten Kromberg (remote)<\/p>\n<p>Morten returned for a second presentation, this one looking at tooling for migrating to Dyalog from other APL implementations. There are tools to swap language constructs for Dyalog cover functions that reproduce the original behaviour \u2014 and you wouldn&#8217;t necessarily expect it, but even <code class=\"language-apl\">\u2227\/<\/code> (<em>and-reduction<\/em>) and <code class=\"language-apl\">\u2228\/<\/code> (<em>or-reduction<\/em>) can need special handling to behave identically for certain arguments.<\/p>\n<p>GUIs are often the trickiest part of any migration. Often, the pragmatic answer is to move to a conventional web stack, such as React, but sometimes a customer would rather retain the native Windows GUI behaviour intact through the migration. For that, there&#8217;s the <code class=\"language-apl\">\u2206WI<\/code> emulator for\u00a0APL+Win&#8217;s\u00a0<code>\u2395WI<\/code>\u00a0that is being developed by Davin Church. In the past we&#8217;ve even seen an APL2 GDDM terminal interface migrated to an HTML\/SVG-based emulator. Looking further ahead, the path from <code class=\"language-apl\">\u2206WI<\/code> to <a href=\"https:\/\/github.com\/Dyalog\/ewc\/\" target=\"_blank\" rel=\"noopener\"><code class=\"language-apl\">eWC<\/code><\/a> could let migrated (or original Dyalog-native) GUIs run cross-platform inside HTMLRenderer or a browser without much further refactoring.<\/p>\n<p><strong>Parsing User Input for Database Normalisation<\/strong><br \/>\nMark Wolfson and Kori Smith, BIG<\/p>\n<p>Mark is a familiar face at Dyalog events; this time he was joined by Kori Smith to talk about the work BIG does in inventory analysis and data aggregation for the jewellery industry \u2014 highly customised data processing for approximately 1,000 customers. The case study they explored was the perennial problem of inconsistent, hand-entered, product descriptions that need to be mapped onto a regular set of fields for database storage and later analysis.<\/p>\n<p>BIG&#8217;s approach combines APL with regular expressions to iteratively refine the processing in a way that can be tuned on an individual customer basis. As Mark and Kori explained, the use case demands more consistency than an LLM can comfortably guarantee, and the mainstream NLP toolkit is overkill for what&#8217;s actually a fairly bounded problem albeit with some\u00a0ambiguities (&#8220;emerald&#8221;, for example, is both a gemstone and a cut of diamond).<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-9452\" src=\"https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_rich_04-1024x538.jpg\" alt=\"Kori Smith presenting\" width=\"584\" height=\"307\" srcset=\"https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_rich_04-1024x538.jpg 1024w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_rich_04-300x158.jpg 300w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_rich_04-768x403.jpg 768w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_rich_04-500x263.jpg 500w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_rich_04.jpg 1200w\" sizes=\"auto, (max-width: 584px) 100vw, 584px\" \/><\/p>\n<p><strong>Dyalog OpenAPI Client Generator<\/strong><br \/>\nHolden Hoover<\/p>\n<p>Holden presented the Dyalog OpenAPI Client Generator, a tool that promises to make it considerably more straightforward to interoperate with the many existing services that publish OpenAPI specifications. Several attendees indicated that they had encountered precisely this issue already, and would benefit from not having to hand-write\u00a0clients for sprawling third-party APIs.<\/p>\n<p>One nice side effect of a machine- and human-readable specification is that it encourages thinking through API design <em>before<\/em> implementation. Holden demonstrated the generator against the <a href=\"https:\/\/open-meteo.com\/\" target=\"_blank\" rel=\"noopener\">Open-Meteo weather API<\/a>, and against the <a href=\"https:\/\/openai.com\/index\/openai-api\/\" target=\"_blank\" rel=\"noopener\">OpenAI API<\/a> \u2014 the latter to generate an introduction-to-APL page complete with examples and an image. He also mentioned the Stark REST Router layer that sits on top of Jarvis, making it easier to expose a Dyalog application to the wider world of HTTP clients.<\/p>\n<p><strong>APL Primitives in the 21st Century<br \/>\nEnhancements in Dyalog v20.0: Arrays, Namespaces, Composition, and Inline Tracing<\/strong><br \/>\nAsher Harvey-Smith<\/p>\n<p>After lunch, Asher gave us a double-bill of presentations about the past and current development of language features in Dyalog.<\/p>\n<p>First, he took us on a whirlwind tour of how the APL primitives have evolved through Dyalog v13.0 to v18.0, with a particular focus on extensions and new primitives motivated by <a href=\"https:\/\/aplwiki.com\/wiki\/Leading_axis_theory\" target=\"_blank\" rel=\"noopener\">leading axis theory<\/a>. This is the idea that functions applied along the first axis can be used to apply to sub-arrays, or between collections of sub-arrays of two argument arrays, in a consistent and malleable way compared to the ad-hoc nature of <a href=\"https:\/\/aplwiki.com\/wiki\/Function_axis\" target=\"_blank\" rel=\"noopener\">bracket axis<\/a>. He started with short left arguments to <em>take<\/em> (<code class=\"language-apl\">\u2191<\/code>) and\u00a0<em>drop<\/em> (<code class=\"language-apl\">\u2193<\/code>) in Dyalog v13.0, and progressed through to <em>unique mask<\/em> (<code>\u2260<\/code>) which marks unique major cells along the leading axis from the outset.<\/p>\n<p>From there, Asher moved on to new features in Dyalog version 20.0. We saw APL array notation and its integration into the Dyalog session and editor, the ability to write namespace literals analogous to JSON, and inline tracing to step through an expression one function at a time. He explained <em>behind<\/em>\u00a0(<code class=\"language-apl\">\u235b<\/code>) as a complement to <em>compose<\/em>\u00a0(<code class=\"language-apl\">\u2218<\/code>), with the filter idiom <code class=\"language-apl\">\u235b\/<\/code> as his favourite example (for example,\u00a0<code class=\"language-apl\">&gt;\u22180\u235b\/<\/code> to extract positive elements from a list). He concluded with <code class=\"language-apl\">\u2395VGET<\/code>\/<code class=\"language-apl\">\u2395VSET<\/code> for manipulating variable values without resorting to the potentially-dangerous <em>execute<\/em>\u00a0(<code class=\"language-apl\">\u234e<\/code>), and <code>\u2395SHELL<\/code> for more complete and controllable command-line execution from APL.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-9454\" src=\"https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_holden_03-1024x538.jpg\" alt=\"Asher presents a slide about short left arguments\" width=\"584\" height=\"307\" srcset=\"https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_holden_03-1024x538.jpg 1024w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_holden_03-300x158.jpg 300w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_holden_03-768x403.jpg 768w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_holden_03-500x263.jpg 500w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_holden_03.jpg 1200w\" sizes=\"auto, (max-width: 584px) 100vw, 584px\" \/><\/p>\n<p><strong>Jarvis and AI<\/strong><br \/>\nBrian Becker<\/p>\n<p>Brian\u00a0presented an experiment exploring how far a modern LLM could go in building a simple \u2013 but fully functional \u2013 Jarvis\u2011based web service. The target application was a Wordle\u2122\u2011style game, and the model chosen was Google\u2019s Gemini, selected for its easy, low\u2011cost browser access.<\/p>\n<p>Brian began by crafting a prompt that described his requirements for the service. He then asked Gemini to refine the prompt and produce a project plan. Gemini responded with a surprisingly thorough plan, addressing several architectural details that Brian had not explicitly mentioned. When instructed to \u201cdo it all,\u201d Gemini generated an HTML file containing the complete HTML\/CSS\/JavaScript front end,\u00a0an .apln file defining the WordleServer namespace, and\u00a0an .apls DyalogScript file to configure and launch the service. Then followed an iterative debugging loop (run the service, hit an error, paste the error into Gemini, apply the suggested fix, and repeat). Eventually Gemini produced a workable, if not elegant, solution. Brian proposed a cleaner approach, which Gemini incorporated. That single suggestion ended up being Brian\u2019s only code contribution; all other APL, HTML, CSS, and JavaScript was generated entirely by Gemini.\u00a0The final product was a clean, responsive game that Gemini named <em>ARRAYDLE<\/em>. Brian noted that the process might have been even smoother if Gemini had the ability to execute APL code directly.<\/p>\n<p>This experiment reinforced two trends: LLMs are rapidly improving at generating APL code, and they already excel at producing polished HTML\u2011based front ends.<\/p>\n<p><strong>AVG \u2014 A Voxel Game<\/strong><br \/>\nKyle Croarkin<\/p>\n<p>Kyle gave us a glimpse of his experience learning APL since he started in August 2025, and the substantial project he built to test his learning \u2013 AVG, A Voxel Game (essentially, a mini-Minecraft!). He&#8217;d wanted to develop something more meaningful than puzzles but nothing too daunting, so that he could really explore APL\u2019s expressivity and the interpreter\u2019s performance against the demands of a real-time game.<\/p>\n<p>It was particularly nice to hear Kyle describe moments that more seasoned APLers will recognise. Kyle described arriving at a solution for finding invisible cube faces, only to realise it mirrored the structure of <a href=\"https:\/\/www.youtube.com\/watch?v=a9xAKttWgP4\" target=\"_blank\" rel=\"noopener\">John Scholes\u2019 Game of Life<\/a>, giving him the revelatory experience of suggestivity. He talked about how quickly one can iterate on ideas when the notation is terse enough to keep everything on screen, and how APL puts the data right in your face. He was honest about the learning cliff, especially coming from a conventional CS background, and about the things that <span data-teams=\"true\">weren&#8217;t well-suited for APL in any obvious way<\/span> (flood-filling algorithms for light and shadow being a notable example).<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-9451\" src=\"https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_rich_02-1024x538.jpg\" alt=\"Kyle presents A Voxel Game\" width=\"584\" height=\"307\" srcset=\"https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_rich_02-1024x538.jpg 1024w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_rich_02-300x158.jpg 300w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_rich_02-768x403.jpg 768w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_rich_02-500x263.jpg 500w, https:\/\/www.dyalog.com\/blog\/wp-content\/uploads\/2026\/05\/blog_dyna26_rich_02.jpg 1200w\" sizes=\"auto, (max-width: 584px) 100vw, 584px\" \/><\/p>\n<p><strong>The APL Trust<\/strong><br \/>\nMark Wolfson<\/p>\n<p>Mark closed the day with a talk about <a href=\"https:\/\/theapltrust.org\/\" target=\"_blank\" rel=\"noopener\">The APL Trust<\/a>, a charitable organisation looking for applications for projects that either do work with\/in APL or that benefit the APL community and ecosystem more broadly. As an example, a recent grant has supported the development of the <a href=\"https:\/\/dyalog.github.io\/APL387\/\" target=\"_blank\" rel=\"noopener\">APL387 font<\/a>. Mark is also now an official Dyalog agent for North America, helping to support existing and prospective customers with their use of Dyalog.<\/p>\n<h2>Q&amp;A and Conversation<\/h2>\n<p>The day was concluded with a Q&amp;A session that gradually broadened into a more general discussion, touching on the ongoing challenges of promoting APL such as the glyphs, onboarding more generally, engaging with communities beyond the existing APL world, and the difficulty commercial users sometimes face in sharing their use cases without revealing industry secrets. None of these are new problems, but it&#8217;s always useful to discuss them together.<\/p>\n<h2>In Conclusion\u2026<\/h2>\n<p>DYNA26 was a great day, well attended and warmly received. Conversations extended beyond the scheduled breaks and continued afterwards when we went for dinner and drinks.<\/p>\n<p>The next user meeting will be <a href=\"https:\/\/usermeeting.dyalog.com\/\" target=\"_blank\" rel=\"noopener\">Dyalog &#8217;26<\/a> in Eastbourne, U.K., on 12-16 October. We hope to see many of you there.<\/p>\n<hr \/>\n<p><em>Materials and recordings from DYNA26 will be added to the <a href=\"https:\/\/www.dyalog.com\/north-american-user-meetings\/dyna26.htm\" target=\"_blank\" rel=\"noopener\">event webpage<\/a> as they become available.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>In April we hosted DYNA26, our latest Dyalog North America user meeting. We returned to midtown Manhattan for a day of presentations, demonstrations, and the sort of impromptu conversations that only happen when APLers are in the same room. Part &hellip; <a href=\"https:\/\/www.dyalog.com\/blog\/2026\/05\/dyna26-a-review\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":11,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[59],"tags":[],"class_list":["post-9328","post","type-post","status-publish","format-standard","hentry","category-dyna"],"_links":{"self":[{"href":"https:\/\/www.dyalog.com\/blog\/wp-json\/wp\/v2\/posts\/9328","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dyalog.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dyalog.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dyalog.com\/blog\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dyalog.com\/blog\/wp-json\/wp\/v2\/comments?post=9328"}],"version-history":[{"count":28,"href":"https:\/\/www.dyalog.com\/blog\/wp-json\/wp\/v2\/posts\/9328\/revisions"}],"predecessor-version":[{"id":9459,"href":"https:\/\/www.dyalog.com\/blog\/wp-json\/wp\/v2\/posts\/9328\/revisions\/9459"}],"wp:attachment":[{"href":"https:\/\/www.dyalog.com\/blog\/wp-json\/wp\/v2\/media?parent=9328"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dyalog.com\/blog\/wp-json\/wp\/v2\/categories?post=9328"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dyalog.com\/blog\/wp-json\/wp\/v2\/tags?post=9328"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}