Excel is outdated. I thought I loved LET() and LAMBDA(), but I can no longer spend my waking life with VBA and reflectionless formulas. Just in the same way that Julia was created to satisfy greedy linguists, I should not feel ashamed for wanting Julian spreadsheets.
In reviewing similar topics to this request, I see that macros may not currently have direct access to named values/variables. My inchoate dream is to narrow down a declarative spreadsheet dialect that uses the tersest-possible syntax to avoid frightening my non-developer coworkers with “code” (Excel’s formula bar is essentially a DSL, but I digress). By creating the spreadsheet anew upon each run, I wonder if this would allow for quicker structural edits, which currently occupy far too much of my time, by faking immutability through a sort of Thesean ship approach.
Is it at all possible to pass values directly to @macro calls? I originally tried instantiating cell functions dynamically to avoid the infamous macro compilation overhead (e.g., “A1(expr)”, “B2(expr)”, …, depending on the underlying file shape and size), but the macro syntax is too clean by comparison. It feels like constructing spreadsheets directly from the command line, and I want to keep it. Can I eat my cake, or merely claim possession?
Thank you all in advance for your constructive and/or destructive criticism!