> 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
Yes that's why haxe includes Neko. Nicolas -- Neko : One VM to run them all (http://nekovm.org)
