You are thinking of neko as a language, and I understand that. But it is also a vm. Well actually there is a language, and there is a vm, and they are separate. You have created a naming convention that equates them, but you could very well have named the vm as Neko and the language that is close to the neko instruction set something else.
In any case, I am talking about the vm, as a tool for haxe developers. I agree that few people will write code in neko. But just like php ships with an easy to install interpreter, haxe should ship with an easily installed interpreter. There is no difference (from an installation perspective) between php and haxe/neko. I think haxe may have its greatest success on the server side and so I think making it easy for those users to install a package should be the mindset. Hank On 6/14/06, Nicolas Cannasse <[EMAIL PROTECTED]> wrote:
> But actually... seriously, why not target newbies. > > Neko is just a VM. If newbies can use java and the JVM (which is super > simple to install) why not make neko just as simple. > > Hank I can't see myself promoting both haXe and Neko as the "best solution" ;) Neko has been designed to be an intermediate language. Although you can read and write Neko source code, it's not meant to be programmed like PHP. Nicolas -- Neko : One VM to run them all (http://nekovm.org)
-- Neko : One VM to run them all (http://nekovm.org)
