nile VS kesh

>you may or may not be aware that when he headed vpri, they did some substantial research into some of the other important ways to organize software, including things like array languages, david p. reed's work on spatially replicated computation, and cooperating communities of specialized solvers.

I'm very interested in knowing what array languages they were researching. The only thing I can find is Nile[1] but from the examples it doesn't look like an array language to me.

[1] https://github.com/damelang/nile

Again, "compile-to-JS" is too broad of a term. It is very difficult to understand what you are looking for. You can have everything in there from languages that just add little bits to JS like TypeScript & CoffeeScript all the way to research languages like Nile and extremely powerful languages like ATS or Rust.

Can you link to both the Maru community and the reborn Nile work? I've always tried to follow the latter, but [1] seems to be the only place to find information and it's been silent for a long time.

[1] https://github.com/damelang/nile/issues/3

I have something similar in kesh, where : is the assignment operator and the type/signature may be "assigned" before the value:

I'm not OP, in case you thought that :) kesh lives here. I tried incorporating some of the ideas discussed here, but posponed it to a later language, which I'm still thinking about.

This is a great idea that I've adopted for my PL. I took it a step further and also allow extensions of the core language to be specified, including profiles.

My (non-existing) language kesh, designed to compile to TypeScript, has expression blocks. That was one of my first decisions.

Still no work on a compiler, but more work on the documentation of kesh.

I'm working on kesh, but it's only at the design stage. I have tried to make it simple yet powerful, so I thought I'd mention it even though you can't use it.

I tried to distill down the most essential features of TS/JS (functional, prototypal) and then come up with new syntax and semantics that was minimal, orthogonal and hopefully easy to learn and use. The result is kesh and na.

I like the way you think. I had the same goal with kesh. A minimal syntax is easier on the eye and lets you focus on the actual code.

I'm only at the drawing board stage of kesh, a simple little PL that one day might possibly transpile to TypeScript. Not a single line of compiler code has been written so far, it's still all about syntax design and exploring ideas. kesh is mostly a pastime activity and something I can ponder over when I'm bored or can't sleep (which may be the reason I can't sleep).