@RGS @Adám I've sent you a blog post update following your feedback.

@xpqz Great!

@Adám, is it possible to share here too the meet link for BAA's today meet ? Good evening btw :)

@milia That was last week and the next one is next week I believe (unless there's another one I'm not aware of)

oh yes I forgot

@milia It isn't until next week, remember? BAA_this_week←~{2|⍬2⊃¯11 ⎕DT'Z'}

I thought it was this week

yeah

forgot lol

sry + thx :)

BAA_this_week

hmmm

dyalog) BAA_this_week

not sure what arguments this function takes :|

⋄⎕←~{2|⍬2⊃¯11 ⎕DT'Z'}⍬

@xpqz 0

(Wonder why I put ~ outside…)

BAA_this_week 1

{2|⍬2⊃¯11 ⎕DT'Z'} 2

You need a leading ⎕← or ⋄ to activate the bot.

Also, it has no state, so you can't use a definition from a previous message.

oh !

@Adám I like, get the 50% of what you've said. I think I need to study more before I start pressing buttons like a coding monkey xD

@milia Have you seen my beginner's guide to APL? xpqz.github.io/learnapl

@xpqz I have this in the first tab of my browser :D It looks pretty awesome. I need to chill a bit and look into it. Thanks !

@milia Always happy to explain.

APL Cultivation is also a very good follow up read (and should totally be made into a book!)

@FawnLocke Agreed. We just need a volunteer. They can get all the honour.

@Adám It's already the basis of the intro jupyter notebooks on TryAPL, so it'd be nice if it was a jupyter book as well like the new mastering.dyalog.com and xpqz/learnapl

@FawnLocke this looks very interesting too, I'll bookmark it, thanks !

@RikedyP Only a couple of the intros. We never got around to making any kind of comprehensive coverage in our tutorials.

@Adám What did you have in mind? I'd be interested.

The format is (obviously) a group conversation -- do you envisage this being kept, or distilling it down to the thread you're weaving?

@xpqz I'm gonna butt in and say that whenever relevant, the 3rd party questions and comments should be included in the text.

I do remember some questions/comments being highly relevant.

The bulk of the work would be filtering those and figuring out a way of putting everything together in writing in a cohesive way.

↑ I imagine.

@xpqz Yeah, what he said. ↑

@xpqz Wait, you'd be interested in what I had in mind, or you'd be interested in authoring another book, based on my lessons?

I'd be interested in volunteering for converting your lessons according to your wishes so that they can be published as notebooks

@xpqz Oh OK. Well, my understanding is that your current APL book doesn't have complete coverage of built-ins (correct me if I'm wrong), so maybe it'd make a good companion collection where there are some introductory notebooks (they might be those already created) on general syntax, and then going going through the built-ins one-by-one, in the narrative form and mini-tasks I used, only adding things when I was unclear enough that the audience had questions.

Absolutely - my book has a pretty narrow core focus. I learnt a lot from your cultivations. How about I take a stab at one chapter and we can see how that looks?

Of course. Go for it!

@Adám Right, lesson 9.ipynb in your mailbox.

Whoa, that's some speed.

Well, all the content's written...

@Adám today at my team's weekly meeting at work I did a short introduction to APL, its history and importance and suggested them to try out tryapl.org, and if they enjoy it and would like to learn more about the language, to ping me so that I invite them in our friendly community over Discord.

We have some pretty bright people at work and I'm certain they'd only benefit if they would "bother" learning the language. Anyhow, I always enjoy sharing with good colleagues some hidden gems that I might discover randomly once in a while.

@milia Oh wow. Good going. Let me know if I can be of any help.

will surely do :) I hope that 1-2 of them join the server. We'll see.

If any of them don't have a Discord/Matrix account (or rather, don't want to have), but have a Stack Exchange account, then they can come here too.

Imagine @Adám, if after say 5-10 years all modern cloud infrastructures such as GCP, AWS, Azure would have clients that communicate with their APIs via Dyalog APL. I think this is now in the sphere of sci fi, but one can always dream for a better world.

I'm not sure that's really a sweet spot for APL. However, it'd be nice if they had off-the-shelf APL containers for easy deployment of APL-based services.

They all of them do have SO account (part of our work is to do community support for BD GCP products at SO), so yes I'll surely share the-apl-orchard tomorrow morning at our team's chat room.

You know about the short url apl.chat?

oh, no :D !

this is so great

I'll do a go/ link for them, so they'll be able to do simply a go/apl.chat and go there :)

@Adám regarding the containers I guess it's up to Google/Amazon/MS if they'll create APL-in-the-box containers.

@milia There are these ready-to-go.

@Adám amazing. I have to admit that I've fallen behind the composers & k8s paradigm, but I understand that they're of crucial importance in modern software development

they're everywhere nowdays

it's good to know that Dyalog is keeping up with the modern tech

I'd say "catching up" is more precise.

We're just now adding #! scripting – only 40 years late.

oh :|

well at least you're at the right direction

@Adám was the #! scripting possible with GNU APL ?

It is. (GNU APL is much younger than Dyalog.)

And Dyalog APL is the "young one" in the APL family!

this sounds somewhat contradictory ?

@Adám also thanks for your edits on my user page at aplwiki. I followed your [[wikipedia:lemma|lemma]] pattern and it looks much cleaner now.

@milia Well, IBM released their first APL version in '68 and STSC & IPSA released APL PLUS (which later split into APL*PLUS and SHARP APL) in '70, while Dyalog released in '83.

@milia Hint: If you want the display text to match exactly the WP title, it is enough to write [[wikipedia:title|]]

On '68 was the APL/360?

ohoh

APL\360, but yes.

heh, my first thought was to put \ but.

\ is expand while / is compress. APL was expanding the capabilities of IBM/360.

I took some time in the family graph of APL you've created. It's pretty interesting how many languages have been influenced by APL\360

oh !

notation again

I'll go check if I can remove some bytes from the aplwiki page, thx for the tip

@milia Don't waste your time; they'll expand to the full form when you submit.

ok, thx. I'll go back to @xpqz's book

:)

@xpqz Oh, someone noticed that you're not serving the fonts. Maybe settle on DejaVu Sans Mono and serve that?

I have no idea how, but I’m sure I can find out.

The problem is that Chromium based browsers prefer attempting to compose missing glyphs from their Unicode equivalences rather than falling back to a different font. However, they don't (or can't, I'm not sure) check if the font supports such composition, and when it doesn't, people end up seeing ≡/ instead of ≢.

@xpqz Can you not inject arbitrary CSS?

Yes, I believe there is a way. I can probably steal it from @RGS.

Or from APL Wiki:

@font-face {
  font-family: "codefont";
  src: local("DejaVu Sans Mono"),
       local("APL385 Unicode"),
       local("SImPL"),
       url(aplwiki.com/images/7/75/DejaVuSansMono.ttf) format('truetype');
}

Ok, will look tomorrow.

Thanks.

@xpqz It's not stealing if I give it away: github.com/Dyalog/MDAPL/blob/master/book/_static/custom.css

Not sure if that's what you wanted :P

1 + / 1 2 3
1 2 3

any idea what the output is 1 2 3 ?

why output is 1 2 3 ?

@elliptic00 Sure, this returns the sums over sliding windows of size 1.

sliding window.. I see

n-wise reduce.. in RIDE doc

@elliptic00 very easy to see if you use ,/ as the function:

⎕← 3 ,/ 'execution' ⋄ ⎕← 2 ,/ 'execution' ⋄ ⎕← 1 ,/ 'execution'

@RGS
┌───┬───┬───┬───┬───┬───┬───┐
│exe│xec│ecu│cut│uti│tio│ion│
└───┴───┴───┴───┴───┴───┴───┘
┌──┬──┬──┬──┬──┬──┬──┬──┐
│ex│xe│ec│cu│ut│ti│io│on│
└──┴──┴──┴──┴──┴──┴──┴──┘
execution

@RGS Is it now? Why isn't the last result ⎕←,¨'execution'?

@Adám
┌─┬─┬─┬─┬─┬─┬─┬─┬─┐
│e│x│e│c│u│t│i│o│n│
└─┴─┴─┴─┴─┴─┴─┴─┴─┘

@Adám That's an excellent question regarding the details. I think my three examples show clearly what the sliding window does.

nice, thx:

⍝ is there way to sliding along a vector  1 2 3 4
      ⍝  (1 2 3 4) ,/ 'banana'

⎕←1 2 3 4 ,/¨⊂ 'banana'

@Adám
┌──────┬────────────────┬─────────────────┬────────────────┐
│banana│┌──┬──┬──┬──┬──┐│┌───┬───┬───┬───┐│┌────┬────┬────┐│
│      ││ba│an│na│an│na│││ban│ana│nan│ana│││bana│anan│nana││
│      │└──┴──┴──┴──┴──┘│└───┴───┴───┴───┘│└────┴────┴────┘│
└──────┴────────────────┴─────────────────┴────────────────┘

why we need the enclose ⊂ ?

all I know is the Enclose convert vector to scalar,

@elliptic00 That's exactly why. Do you understand what happens with ⎕←1 2 3 4 +¨ 10?

@Adám 11 12 13 14

Ok, ⊂'banana' = 10 ?

Yeah, kind of. the scalar is opened and used for each of the vector. Same thing above.

thx:)

f¨ is actually ⊂⍤f⍥⊃⍤0

b←'banana' ⋄ ↑(⍳≢b),/¨⊂b
┌──────┬──────┬──────┬──────┬──────┬──────┐
│b     │a     │n     │a     │n     │a     │
├──────┼──────┼──────┼──────┼──────┼──────┤
│ba    │an    │na    │an    │na    │      │
├──────┼──────┼──────┼──────┼──────┼──────┤
│ban   │ana   │nan   │ana   │      │      │
├──────┼──────┼──────┼──────┼──────┼──────┤
│bana  │anan  │nana  │      │      │      │
├──────┼──────┼──────┼──────┼──────┼──────┤
│banan │anana │      │      │      │      │
├──────┼──────┼──────┼──────┼──────┼──────┤

Try to get the suffix and prefix string from a given string, it seems the table is pretty useful for string matching or string searching..

the first column is prefix, and the minor diagonal is suffix

And all the other elements are infixes.

But the mix (↑) adds nonsensical elements.

{(⍳≢⍵),/¨⊂⍵} computes all contiguous substrings.

btw

Yup, was about to say.

(⍳∘≢,/¨⊂)

⍝ how the apl know my ⍵ in this two position (⍳≢⍵,/¨⊂⍵)

And yes, it is quite useful. (Especially for a handful of LeetCodes :P)

(⍳∘≢,/¨⊂) 'banada'

It's a monadic fork, ⍳∘≢ & ⊂ take the arguments then ,/¨ is applied between them.

Can learn more about them in xpqz's book

Or on APL Wiki.

⎕←⍳∘≢,/¨⊂

@Adám
 ┌────┼─┐
 ∘    ¨ ⊂
┌┴┐ ┌─┘
⍳ ≢ /
  ┌─┘
  ,

Thanks!

Is it okay to redistribute the Dyalog interpreter? Also, has Dyalog been built against the musl libc?

Nevermind, docker will work fine :)