Deconstruction and De-Ceremony is needed

[solarsystemic]

J has "dissect" and you can "parenthesize" convoluted one liners and more for APL/J and trees and whatever.

New coders need this (new) for a much more easily Grokable suite of APL languages. All you need is just.... decompose any line or more and provide 1 to X number of unit operations on each line - with an assigned global name like "Y". Gratis to add in the glyph at the end of the line so the newbies can document it as needed. Deconstruct then people later... can dedeconstruct. Deceremonialize every line if needed. The problem though with that kind of transparency the Emperor won't have any clothes. The other benefit is many of new users will actually prefer for not the usual 7 to 10 lines of Javascript to APLs 1 line (12.5 for UIUA) but more like 3 to 1. I assure you this would be much much easier than making a 'dissect'. Call it maybe 'Grokker"

[kaikalii]

I'm not really able to understand what you are asking for. Can you please give an example?

[solarsystemic]

Hello: Here is a J example in Github below and they are worse than this. J fosters less documentation and fewer lines (intentionally). I was a paid APL and J around 30 years ago around 1% of my total efforts and hobbyist now. Back then was more like Vanilla code with even "DOS" graphics. I think you changed to a tree arrangement for easier compiling or similar so perhaps a Grokker would be much much much easier than J's Dissect. If newbies could just copy and paste UIUA code and click on the decomposer Grokker then all of those hours of trying to decipher many of the lines - then each decomposed chunk can be deregailed via trying the much smaller snippets - line by line. Each line would have the usual global name. -"Y" perhaps or Y1,Y2,Y3...., then becomes the next line of the decomposed line. This J line below would be 1-12 or less "chunks" in line and the series of chunks 'works' from the first line to the first three lines and then all of the perhaps many lines would 'work'. At the end of each line the document glyph will be right there for each snippet noted as needed. fracto16 =: ;@:((,&' ')&.>)@:(,&(<'/16'))@:((({.&.".)@:(,&' 0'))&.>)@:(< onpiecesbetweenm '''') ^: (''''&e.) Experts would still be useful to select say 5 lines via "deconstruction". This way "any" programmer would then just copy/paste "appropriate" code and Grokker. If the programmer wants to add in any notes at the end why not. This way they would need to operate each decomposed line before any documentation. Another benefit is you won't need as many instructional videos! There is some kind of law of physics where APLers get better and perhaps more intelligent and then the already excessive long lines get longer! Then the documentation disappears lastly. Example: Grokker (+/ % # ) 1 2 3 NB. for average 1. y1=: # 1 2 3 NB. 2. y2=:+/1 2 3 NB. 3. y3 =:y2 % y1 NB. or similar and also it would be great for - Grokker 3;'code' - and then the first or more lines would be 3 unit statements each line. Grokker 3;'(+/ % # ) 1 2 3' 1. y1=: (+/ % # ) 1 2 3 or Grokker 1;' X' where X for the code. How about 'Uikker' instead oops....... better for 'UIcog'. It should be so easy like junior high school UIUA! The ultimate test (very useful) would be the UIcog de"constructing" that great UIUA game code around 6 weeks ago. BHC

…

On Tue, Jan 14, 2025, at 3:07 PM, Kai Schmidt wrote: I'm not really able to understand what you are asking for. Can you please give an example? — Reply to this email directly, view it on GitHub <#647 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYELGSL7G3NB77QIMKSLMH32KWKCZAVCNFSM6AAAAABVF55Y5WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBTGY4DONQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>