On
I was very inspired by Ioke. Ioke ebnf syntax is a dozen of lines. But it can give me all I liked in Forth, C++ and JS. Also Ioke is brave to use characters beyond ascii-127 for operators.
Human mind can only deal with very simple things, but can abstract them into high order structures easily, and then deal with the abstraction as with the new simple thing. And then take few abstractions together and abstract on them again and again. Each time using some different ways to generalize simple things into a very simple thing.
Ioke allows you to create new ways to express your ideas on each different level of abstraction. You need a new syntax or new way to express on each level. You need a tool to create tools. And you do not want to get lost in nor abstration nor detail.
Ioke author sees properties of human mind, better than authors of other languages who are not brave enough to see that something is not only behind the monitor but also in front of it, which is a human being. But they are not to blame, because users of languages are blind to their own mind machinery as well. So Ioke is really a brave attempt to attack on flatness of other languages, and, therefore, an attack on flatness of the way we are learned to think.
On
Ioke is quite an interesting language to play with to create DSLs. I find the simplistic syntax (everything, even control flow, is a message) that can be expanded interesting. Macro support in Ioke is great (retrieve parts of message before they are evaluated [or 'activated']).
Ioke is obviously still a very young project, but very promising.
Thinking about it further, I am a bit conflicted regarding the simplistic syntax as I'm still hoping for a tad more syntactic sugar -- for example for control blocks which are more expressive IMHO when using special syntax -- rather than being pure messages that must be implemented with the same bracketed syntax as any other message.
I guess this is a matter of taste -- do you keep the language definition simple and 'pure' or do you 'taint' it with more syntax and make it a bit more expressive?
On
Seems interesting, but is currently just a proof of concept.
If you need something similar now, just take a look at IO language
AFAIK this is just a one-man-show. It seems extremely unlikely that one person will be able to undertake all the work necessary to make a programming language popular, e.g. writing tools, libraries, etc.
So unless he can get a big company to back him and use his language or establish a community of IOKE developers, I would suggest his languages is doomed to failure, ho matter how performant/elegant it is.
On a more superficial level, I dislike the name IOKE, mostly because it's not at all obvious how it should be pronounced.