Whiteside talks of eventually adding an interface layer that manages method registration, so methods can be "called directly without having to unpack their parameters from the argument array."
Slate: a grand experiment
BeanShell, NQL, and Simkin are all bottom-line products that aim to make a difference in the rush-to-market of end-user applications. Slate's origins are more academic; it embodies research as specific aspects of user-interface and language design.
Slate borrows recognizable features from at least a dozen languages. To a developer, it feels like Smalltalk because it's fully object-oriented, highly interactive, and manifested as a total working environment, rather than an isolated language processor. Slate's syntax is like Self or Beta's, its semantics are functional and emphasize immutable objects, and it is highly reflexive, like Forth or Scheme. A Slate working environment is readily customizable, in that new languages are available through sophisticated parsing objects.
Slate implements most of the TUNES (Tunes is a Useful, Nevertheless Expedient, System) metaprogramming project, and is currently experimental. While it does interesting things on the project team's computers, it's hard to develop practical new applications with it. Slate appears to be at about the point Linux was in early 1992, or perhaps more precisely, where Hurd is now. On the other hand, Slate has achieved interesting milestones in the year 2000, and will interest those who want to be part of the future of computing language design and use.