Ola Bini, one of the big guys behind JRuby, is developing a new programming language called: IOKE. It's influenced by lisp, smalltalk and ruby. Share your thoughts about this new dynamic programming 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.
Seems interesting, but is currently just a proof of concept.
If you need something similar now, just take a look at IO language
Ola is not just "one man". He's "one superman".
I found Ioke after looking at Io (and being a Ruby programmer of about five years). So far, I love the language. The core is very small, and quite intuitive. He's currently marrying Ioke with the JVM, but he's claimed that it wouldn't be too difficult to port it to JavaScript and throw it on V8 (if such a thing was desirable). I imagine he'll stick with the JVM, as this theoretically allows her to utilize other Java libs.
The documentation is clear and plentiful (a side-effect of using TDD which generate docs). The language model is clear enough to understand. Its macros are powerful. Its prototype-based object model is easy to understand.
As a language, I'm in love. I can't wait until he focuses on speed.
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?