@NikosAlexandris APL is actually much less complex than most programming languages. It is especially suited for data-scientists to write and explore their own algorithms instead of having to lean on a programmer who doesn't understand the field. It might look foreign at first, much like Greek looks foreign to those that only know Latin. I'd be happy to give you a quick tour.
@Razetime Only temporarily. Next time someone (you included) need to load the code, simply use Link.Import or Link.Create and it is all set up for you.
We'd also add it to the command line, so you could actually have a RIDE config (you know you can have as many configs as you want, right?) for each project, and it'd be linked when you begin.
Yes, I've tried googling. Yes, everything works fine in TryAPL. Yes, I have touched a keyboard before. I just seem to be missing something bleedingly obvious
Ohh, thank you!
A lot less straight forward than I expected - I no longer feel bad for not guessing that
@0xACE That could work. I guess I'll try sticking with the standard keybindings for now (or get sidetracked creating a VSCode plugin). The TryAPL bindings were just intuitive enough that I could usually guess them
@user13724060 You should now have access. Welcome to the APL Orchard. Since you're new to Stack Exchange chat, I recommend having a look at apl.wiki/APL_Orchard#Features.
Basically, 18.0 had a ton of optimisations made from 17.0 with 17.1 released in the middle as a minor update to 17.0. However, some optimisations in 18.0 were found to have bugs, and so the next version is re-branched from 17.1 with 18.0 being a dead-end. We are carefully porting optimisations from 18.0, but my current development version doesn't have ⊃⍤⍋ optimised.
Yes, it will have all the features of 18.0 (and probably proper scripting, a single system function for item metadata, three nice dark themes, and more). This is all for the next-to-be-released version after 18.0.