ivy VS cognate

I think you might be thinking of Rob Pike's project, unless Russ has been involved?

https://github.com/robpike/ivy

My recent exposure to array programming languages came via a podcast called The Array Cast[1]

Not affiliated, just recommending. The regular co-hosts appear to each be experienced with various array languages such as J, APL, etc. They don't get deeply technical, but it's a nice introduction, especially on explaining the appeal.

A recent episode had Rob Pike (UTF-8, Go, etc.) on to talk about his array based calculator, Ivy[2]

[1] https://www.arraycast.com/

[2] https://github.com/robpike/ivy

I enjoyed russ cox's advent of code series using rob pike's ivy (https://github.com/robpike/ivy), an apl-like calculator

https://www.youtube.com/playlist?list=PLrwpzH1_9ufMLOB6BAdzO...

Ivy is an APL-like programming language created by Rob Pike https://github.com/robpike/ivy

Ivy is another APL like language and one I kind of enjoy, because operations are actually readable and writable.

https://github.com/robpike/ivy

Reminds me a bit of Cognate(https://github.com/cognate-lang/cognate/blob/master/INTRODUC...)

Think I would like Uiua more if it require a space between terms. It wouldn’t be quite as tacit but it would be easier to read and more flexible — you could multi-symbol operators.

Cognate happens to be a simple & readable polish-notation stack language that compiles to C.

This reminds me a lot of Cognate.

Since discovering and being inspired by Cognate, I've begun work on somewhat of a sister language called Adduce, with u/stavro-mueller-beta's blessing. It's honestly been kind of a whirlwind so far - over the course of about a week, I threw together a hacky Javascript interpreter to sketch out my ideas for the language, then rewrote it in Haskell for more permanent development. The language is currently in a mostly working state, though missing a lot of features; the biggest pain points so far have been mostly related to scoping and exception handling, since I'm implementing a dynamically typed, interpreted, mostly-procedural language in a language that is very much neither, and I'd give a tentative guess that just figuring out how to make the latter work at all took over half the development time of the Haskell version so far.